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] Fix elf/tst-dlmopen-twice to support enough link namespaces
Date: Thu, 27 Oct 2022 13:50:03 +0000 (GMT) [thread overview]
Message-ID: <20221027135003.15A9C387688F@sourceware.org> (raw)
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=ae60f3996dc52bad4fd8ecb83315fa974549c0e6
commit ae60f3996dc52bad4fd8ecb83315fa974549c0e6
Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Date: Tue Oct 18 16:33:52 2022 +0100
Fix elf/tst-dlmopen-twice to support enough link namespaces
The test dlmopens 10 namespaces recursively, which requires a glibc
tunable setting, otherwise it may run out of static TLS.
Diff:
---
elf/Makefile | 1 +
elf/tst-dlmopen-twice.c | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/elf/Makefile b/elf/Makefile
index 72178d33ff..399b709a7d 100644
--- a/elf/Makefile
+++ b/elf/Makefile
@@ -2979,6 +2979,7 @@ tst-audit-tlsdesc-ENV = LD_AUDIT=$(objpfx)tst-auditmod-tlsdesc.so
$(objpfx)tst-audit-tlsdesc-dlopen.out: $(objpfx)tst-auditmod-tlsdesc.so
tst-audit-tlsdesc-dlopen-ENV = LD_AUDIT=$(objpfx)tst-auditmod-tlsdesc.so
+tst-dlmopen-twice-ENV = GLIBC_TUNABLES=glibc.rtld.nns=10
$(objpfx)tst-dlmopen-twice.out: \
$(objpfx)tst-dlmopen-twice-mod1.so \
$(objpfx)tst-dlmopen-twice-mod2.so
diff --git a/elf/tst-dlmopen-twice.c b/elf/tst-dlmopen-twice.c
index 70c71fe19c..dfa58b1505 100644
--- a/elf/tst-dlmopen-twice.c
+++ b/elf/tst-dlmopen-twice.c
@@ -46,7 +46,7 @@ do_test (void)
recurse (1);
/* Then with nesting. The constant needs to be less than the
- internal DL_NNS namespace constant. */
+ glibc.rtld.nns tunable (which is between 1 and DL_NNS). */
recurse (10);
return 0;
}
next reply other threads:[~2022-10-27 13:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 13:50 Szabolcs Nagy [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-23 14:40 Szabolcs Nagy
2022-10-26 15:10 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=20221027135003.15A9C387688F@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).