From: Florian Weimer <fweimer@redhat.com>
To: Noah Goldstein <goldstein.w.n@gmail.com>
Cc: GNU C Library <libc-alpha@sourceware.org>,
Linux API <linux-api@vger.kernel.org>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Jeremy Linton <jeremy.linton@arm.com>,
Rich Felker <dalias@libc.org>
Subject: Re: Bringing rseq back into glibc
Date: Thu, 18 Nov 2021 19:55:44 +0100 [thread overview]
Message-ID: <87mtm1e1jj.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAFUsyfKGOCk9vhWTsfP2tH1-P=iYe41vCxbUdfx-b3Oa9ma7iw@mail.gmail.com> (Noah Goldstein's message of "Thu, 18 Nov 2021 12:42:53 -0600")
* Noah Goldstein:
> On Thu, Nov 18, 2021 at 4:17 AM Florian Weimer via Libc-alpha
> <libc-alpha@sourceware.org> wrote:
>>
>> I would like to bring back rseq for glibc 2.35. I propose the following
>> steps:
>>
>> 1. Enable rseq registration in glibc, for internal use only. This time,
>> put the rseq area into struct pthread, not into a initial-exec TLS
>> symbol. (This helps to avoid with initial-exec TLS bloat with dlopen
>> and simplifies initialization somewhat.)
>
> Isn't THREAD_SELF also implemented in TLS? Or am I missing
> something?
THREAD_SELF uses a pointer in the thread control block, and that pointer
is not replicated for different libc.so.6 copies with dlmopen (like the
rest of the TCB and struct pthread).
Thanks,
Florian
next prev parent reply other threads:[~2021-11-18 18:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 10:17 Bringing rseq back into glibc Florian Weimer
2021-11-18 16:32 ` Mathieu Desnoyers
2021-11-18 16:54 ` Florian Weimer
2021-11-18 17:52 ` Mathieu Desnoyers
2021-11-18 18:42 ` Noah Goldstein
2021-11-18 18:55 ` Florian Weimer [this message]
2021-11-18 18:48 ` Cristian Rodríguez
2021-11-18 19:41 ` Mathieu Desnoyers
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=87mtm1e1jj.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=dalias@libc.org \
--cc=goldstein.w.n@gmail.com \
--cc=jeremy.linton@arm.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-api@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=vincenzo.frascino@arm.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 NNTP newsgroup(s).