public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Szabolcs Nagy <nsz@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc/arm/morello/main] cheri: malloc: disable capability narrowing on some tests
Date: Wed, 23 Nov 2022 14:50:37 +0000 (GMT)	[thread overview]
Message-ID: <20221123145038.1DE68385E001@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=c38427f52d5386a25650ed982fa9a4af596a3f34

commit c38427f52d5386a25650ed982fa9a4af596a3f34
Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Date:   Fri Oct 7 16:05:29 2022 +0100

    cheri: malloc: disable capability narrowing on some tests
    
    malloc/tst-malloc-backtrace tests heap corruption.
    malloc/tst-dynarray uses malloc_debug wrappers that access internals.

Diff:
---
 malloc/Makefile | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/malloc/Makefile b/malloc/Makefile
index 4e32de2a0b..0d40188bc1 100644
--- a/malloc/Makefile
+++ b/malloc/Makefile
@@ -88,6 +88,7 @@ tests-exclude-hugetlb1 = \
 	tst-interpose-thread \
 	tst-interpose-static-nothread \
 	tst-interpose-static-thread \
+	tst-malloc-backtrace \
 	tst-malloc-usable \
 	tst-malloc-usable-tunables \
 	tst-mallocstate
@@ -159,6 +160,8 @@ libmemusage-inhibit-o = $(filter-out .os,$(object-suffixes))
 libc_malloc_debug-routines = malloc-debug $(sysdep_malloc_debug_routines)
 libc_malloc_debug-inhibit-o = $(filter-out .os,$(object-suffixes))
 
+tst-malloc-backtrace-ENV = GLIBC_TUNABLES=glibc.mem.cap_narrowing=0
+
 $(objpfx)tst-malloc-backtrace: $(shared-thread-library)
 $(objpfx)tst-malloc-thread-exit: $(shared-thread-library)
 $(objpfx)tst-malloc-thread-fail: $(shared-thread-library)
@@ -331,12 +334,14 @@ $(objpfx)tst-interpose-static-thread: \
   $(objpfx)tst-interpose-aux-thread.o $(static-thread-library)
 
 tst-dynarray-ENV = MALLOC_TRACE=$(objpfx)tst-dynarray.mtrace \
+		   GLIBC_TUNABLES=glibc.mem.cap_narrowing=0 \
 		   LD_PRELOAD=$(objpfx)libc_malloc_debug.so
 $(objpfx)tst-dynarray-mem.out: $(objpfx)tst-dynarray.out
 	$(common-objpfx)malloc/mtrace $(objpfx)tst-dynarray.mtrace > $@; \
 	$(evaluate-test)
 
 tst-dynarray-fail-ENV = MALLOC_TRACE=$(objpfx)tst-dynarray-fail.mtrace \
+			GLIBC_TUNABLES=glibc.mem.cap_narrowing=0 \
 			LD_PRELOAD=$(objpfx)libc_malloc_debug.so
 $(objpfx)tst-dynarray-fail-mem.out: $(objpfx)tst-dynarray-fail.out
 	$(common-objpfx)malloc/mtrace $(objpfx)tst-dynarray-fail.mtrace > $@; \

             reply	other threads:[~2022-11-23 14:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-23 14:50 Szabolcs Nagy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-10-27 14:00 Szabolcs Nagy
2022-10-26 15:22 Szabolcs Nagy
2022-10-12 14:19 Szabolcs Nagy

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=20221123145038.1DE68385E001@sourceware.org \
    --to=nsz@sourceware.org \
    --cc=glibc-cvs@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).