From: Florian Weimer <fweimer@redhat.com>
To: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Joseph Myers <joseph@codesourcery.com>
Subject: Re: [PATCH glibc 0/3] Restartable Sequences enablement
Date: Wed, 03 Jun 2020 15:40:44 +0200 [thread overview]
Message-ID: <877dwow9lv.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <878sh4xshf.fsf@oldenburg2.str.redhat.com> (Florian Weimer via Libc-alpha's message of "Wed, 03 Jun 2020 14:07:40 +0200")
* Florian Weimer via Libc-alpha:
> This series unfortunately needs to be rebased (with conflicts) on
> current master.
>
> There is a new elf/tst-auditmany failure, showing bug 26076, but
> actually caused by bug 26075 (I think). I will attempt to work around
> these two issues, which are independent of the rseq changes.
Mathieu, it turns out that a change like this is needed:
diff --git a/elf/dl-tls.c b/elf/dl-tls.c
index fa03234610..817bcbbf59 100644
--- a/elf/dl-tls.c
+++ b/elf/dl-tls.c
@@ -31,7 +31,7 @@
/* Amount of excess space to allocate in the static TLS area
to allow dynamic loading of modules defining IE-model TLS data. */
-#define TLS_STATIC_SURPLUS 64 + DL_NNS * 100
+#define TLS_STATIC_SURPLUS 64 + DL_NNS * 176
/* Out-of-memory handler. */
I think you can just put that into the main rseq patch. This change
needs to be mentioned in the commit message, of course.
With this change, elf/tst-auditmany passes again for me.
The increase (76 bytes) is larger than 32 bytes because we have not done
this in quite a while. The cost in terms of additional TLS storage is
quite significant, but it will also obscure some initial-exec-related
dlopen failures.
Conceptually, we could also switch to 64 + (DL_NNS - 1) * 176, an
increase of 1040 bytes over what we have today.
Thanks,
Florian
next prev parent reply other threads:[~2020-06-03 13:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 18:51 Mathieu Desnoyers
2020-05-27 18:51 ` [PATCH glibc 1/3] glibc: Perform rseq registration at C startup and thread creation (v20) Mathieu Desnoyers
2020-06-03 12:05 ` Florian Weimer
2020-06-03 12:22 ` Mathieu Desnoyers
2020-06-03 12:31 ` Florian Weimer
2020-06-03 12:40 ` Mathieu Desnoyers
2020-06-03 17:22 ` Joseph Myers
2020-06-04 11:10 ` Mathieu Desnoyers
2020-06-04 17:46 ` Joseph Myers
2020-06-11 17:47 ` Mathieu Desnoyers
2020-06-11 20:26 ` Joseph Myers
2020-06-18 12:22 ` Szabolcs Nagy
2020-06-18 13:03 ` Mathieu Desnoyers
2020-06-22 15:33 ` Mathieu Desnoyers
2020-05-27 18:51 ` [PATCH glibc 2/3] Linux: Use rseq in sched_getcpu if available (v9) Mathieu Desnoyers
2020-05-27 18:51 ` [PATCH glibc 3/3] rseq registration tests (v11) Mathieu Desnoyers
2020-06-03 12:07 ` [PATCH glibc 0/3] Restartable Sequences enablement Florian Weimer
2020-06-03 12:27 ` Mathieu Desnoyers
2020-06-03 12:33 ` Florian Weimer
2020-06-03 13:40 ` Florian Weimer [this message]
2020-06-05 17:04 ` Mathieu Desnoyers
-- strict thread matches above, loose matches on Subject: below --
2020-05-01 2:14 Mathieu Desnoyers
2020-05-20 11:44 ` Florian Weimer
2020-05-25 13:52 ` Mathieu Desnoyers
2020-05-25 14:28 ` Florian Weimer
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=877dwow9lv.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=mathieu.desnoyers@efficios.com \
/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).