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] Fix elf/tst-dlmopen-twice not to exhaust static TLS
Date: Fri, 28 Oct 2022 17:44:12 +0000 (GMT)	[thread overview]
Message-ID: <20221028174412.92F2B3858425@sourceware.org> (raw)

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

commit 2eeeee7636cb52a09740598404808def17cf750e
Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Date:   Tue Oct 18 16:33:52 2022 +0100

    Fix elf/tst-dlmopen-twice not to exhaust static TLS
    
    By default glibc only allocates enough static TLS for 4 link namespaces
    including the initial one. So only use 3 dlmopens in the test.
    
    Reviewed-by: Florian Weimer <fweimer@redhat.com>

Diff:
---
 elf/tst-dlmopen-twice.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/elf/tst-dlmopen-twice.c b/elf/tst-dlmopen-twice.c
index 70c71fe19c..a8d7e5e081 100644
--- a/elf/tst-dlmopen-twice.c
+++ b/elf/tst-dlmopen-twice.c
@@ -46,8 +46,8 @@ do_test (void)
   recurse (1);
 
   /* Then with nesting.  The constant needs to be less than the
-     internal DL_NNS namespace constant.  */
-  recurse (10);
+     glibc.rtld.nns tunable (which is 4 by default).  */
+  recurse (3);
   return 0;
 }

                 reply	other threads:[~2022-10-28 17:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20221028174412.92F2B3858425@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).