From: Simon Chopin <simon.chopin@canonical.com>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] elf: Do not check for loader mmap on tst-decorate-maps (BZ 31553)
Date: Mon, 22 Apr 2024 07:58:39 -0700 [thread overview]
Message-ID: <CAOOWow054iD09GJKWtB9gJc+Y2eHx9T8XwAOJhbn6KKyDQfX7g@mail.gmail.com> (raw)
In-Reply-To: <c0cbfc45-99cf-4af8-b193-e2636c0491dd@linaro.org>
On lun. 22 avril 2024 10:11:47, Adhemerval Zanella Netto wrote:
> On 22/04/24 07:55, Simon Chopin wrote:
> > On mar. 26 mars 2024 10:47:42, Adhemerval Zanella wrote:
> >> On some architectures and depending on the page size, the loader can
> >> also allocate some memory during dependencies loading and it will be
> >> marked as 'loader malloc'. However, if the system page size is
> >> large enough, the initial data page will be enough for all required
> >> allocation and there will be no extra loader mmap. To avoid false
> >> negatives, the test does not check for such pages.
> >>
> >> Checked on powerpc64le-linux-gnu with 64k pagesize.
> >
> > Tested in similar conditions.
> > Altogether it looks good, I just have one minor whitespace nitpick.
> >
Reviewed-by: Simon Chopin <simon.chopin@canonical.com>
> >> ---
> >> elf/tst-decorate-maps.c | 12 ++++++------
> >> 1 file changed, 6 insertions(+), 6 deletions(-)
> >>
> >> diff --git a/elf/tst-decorate-maps.c b/elf/tst-decorate-maps.c
> >> index 85ba5ce939..6d04344ba2 100644
> >> --- a/elf/tst-decorate-maps.c
> >> +++ b/elf/tst-decorate-maps.c
> >> @@ -56,7 +56,6 @@ struct proc_maps_t
> >> int n_user_threads;
> >> int n_arenas;
> >> int n_malloc_mmap;
> >> - int n_loader_malloc_mmap;
> >
> > OK
> >
> >> };
> >>
> >> static struct proc_maps_t
> >> @@ -82,8 +81,12 @@ read_proc_maps (void)
> >> r.n_arenas++;
> >> else if (strstr (line, "[anon: glibc: malloc]") != NULL)
> >> r.n_malloc_mmap++;
> >> - else if (strstr (line, "[anon: glibc: loader malloc]") != NULL)
> >> - r.n_loader_malloc_mmap++;
> >> + /* On some architectures and depending on the page size, the loader can
> >> + also allocate some memory during dependencies loading and it will be
> >> + marked as 'loader malloc'. However, if the system page size is large
> >> + enough, the initial data page will be enough for all required
> >> + allocation and there will be no extra loader mmap. To avoid false
> >> + negatives, the test does not check for such pages. */
> >
> > Whitespace mixup here? The first line of the comment block appears to be
> > using a different indentation to the rest of the block.
>
> Hum, I used whitespace because it does not really fit for the indentation
> of the 'while'. The rest of patch use tab because it then allows it.
Fair enough.
>
> >
> > Good call on leaving an explicit comment!
> >
> >> }
> >> free (line);
> >> xfclose (f);
> >> @@ -148,8 +151,6 @@ do_test_threads (bool set_guard)
> >> TEST_COMPARE (r.n_user_threads, num_user_threads);
> >> TEST_COMPARE (r.n_arenas, expected_n_arenas);
> >> TEST_COMPARE (r.n_malloc_mmap, 1);
> >> - /* On some architectures the loader might use more than one page. */
> >> - TEST_VERIFY (r.n_loader_malloc_mmap >= 1);
> >
> > OK
> >
> >> }
> >>
> >> /* Let the threads finish. */
> >> @@ -164,7 +165,6 @@ do_test_threads (bool set_guard)
> >> TEST_COMPARE (r.n_user_threads, 0);
> >> TEST_COMPARE (r.n_arenas, expected_n_arenas);
> >> TEST_COMPARE (r.n_malloc_mmap, 1);
> >> - TEST_VERIFY (r.n_loader_malloc_mmap >= 1);
> >
> > OK
> >
> >> }
> >>
> >> free (p);
> >> --
> >> 2.34.1
> >>
prev parent reply other threads:[~2024-04-22 15:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 13:47 [PATCH] elf: Do not check for loader mmap on tst-decorate-maps (BZ 31553) Adhemerval Zanella
2024-04-22 10:55 ` Simon Chopin
2024-04-22 13:11 ` Adhemerval Zanella Netto
2024-04-22 14:58 ` Simon Chopin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOOWow054iD09GJKWtB9gJc+Y2eHx9T8XwAOJhbn6KKyDQfX7g@mail.gmail.com \
--to=simon.chopin@canonical.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).