public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "adhemerval.zanella at linaro dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug malloc/31498] malloc/tst-free-errno-malloc-hugetlb1 test fails on arm64
Date: Tue, 19 Mar 2024 12:34:30 +0000	[thread overview]
Message-ID: <bug-31498-131-oAbiv3R9tC@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31498-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31498

--- Comment #4 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
(In reply to Sam James from comment #2)
> huge pages & malloc internals are beyond me, so I've no idea what else to
> request, but can obtain other things as requested

The hugetlb1 tests should be similar to default malloc ones, the difference is
essentially an extra madvise with either the arena or the brk pointer aligned
to hugetlb size (so I would not expect memory corruptions). I haven't see any
failure on aarch64, but the test-free-errno uses some mmap tricks to trigger
memory exhaustion so I am not sure if this might be related.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2024-03-19 12:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-16 10:45 [Bug malloc/31498] New: " sam at gentoo dot org
2024-03-16 10:45 ` [Bug malloc/31498] " sam at gentoo dot org
2024-03-16 10:45 ` sam at gentoo dot org
2024-03-16 11:00 ` schwab@linux-m68k.org
2024-03-19 12:34 ` adhemerval.zanella at linaro dot org [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-31498-131-oAbiv3R9tC@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).