From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 720E13858D1E; Tue, 19 Mar 2024 12:34:31 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 720E13858D1E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1710851671; bh=x+N5sPfnLLG2QhzYSBYDGfk5BWFO6ukSLERfrHkhFog=; h=From:To:Subject:Date:In-Reply-To:References:From; b=F1SsQLZ6FTOTEj7rEnRp9o6VcxcwSqsoduYtTiNQnFLD6NPHFCyhquJYBn4k8aB4g 1FC7HI9pceocbmEuvBtAbNoBK3KmTpUuEKGRK6gz9FxWERRFWgz5DbO4QBZjx11aaY zc4WWT3Vszzs5t6SckuOr91pbz24aGHF+WBBZQCI= From: "adhemerval.zanella at linaro dot 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: malloc X-Bugzilla-Version: 2.37 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: adhemerval.zanella at linaro dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D31498 --- Comment #4 from Adhemerval Zanella --- (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 align= ed to hugetlb size (so I would not expect memory corruptions). I haven't see a= ny 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. --=20 You are receiving this mail because: You are on the CC list for the bug.=