[Bug 2058466]

[Adhemerval Zanella]

(In reply to Simon Chopin from comment #3)
> Thanks Andreas for pointing me to the page size.
> 
> There's an assumption made in the test that the early allocation code will
> need to grow beyond the initial data page, as those extra pages would be the
> ones marked "[anon: glibc: loader malloc]". However, if the page size is
> large enough, I guess that assumption isn't valid anymore.
> 
> I'll write a patch skipping this particular assertion if the page size is
> 64k or above.

I could reproduce it on a ppc64le VM, and it seems to what you
described: the __minimal_malloc never issues the mmap because the
initial data segment can supply the loader memory requirement.  I think
without a way to trigger the load mmap allocation, it would be better to
just remove the 'loader malloc' check (it might be that we will need to
adjust for possible different page sizes).

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to glibc in Ubuntu.
https://bugs.launchpad.net/bugs/2058466

Title:
  glibc 2.39 test failure on ppc64el: elf/tst-decorate-maps

Status in GLibC:
  New
Status in glibc package in Ubuntu:
  New

Bug description:
  This test fails on Noble/ppc64el

  3775s FAIL: elf/tst-decorate-maps
  3775s original exit status 1
  3775s error: tst-decorate-maps.c:152: not true: r.n_loader_malloc_mmap >= 1
  3775s error: tst-decorate-maps.c:167: not true: r.n_loader_malloc_mmap >= 1
  3775s error: tst-decorate-maps.c:152: not true: r.n_loader_malloc_mmap >= 1
  3775s error: tst-decorate-maps.c:167: not true: r.n_loader_malloc_mmap >= 1
  3775s error: 4 test failures

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/2058466/+subscriptions