From: Florian Weimer <fweimer@redhat.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: John Mellor-Crummey <johnmc@rice.edu>,
libc-alpha@sourceware.org, Ben Woodard <woodard@redhat.com>,
"Mark W. Krentel" <krentel@rice.edu>,
Jonathon Anderson <janderson@rice.edu>,
Xiaozhu Meng <xm13@rice.edu>
Subject: Re: A collection of LD_AUDIT bugs that are important for tools (with better formatting for this list)
Date: Wed, 23 Jun 2021 08:32:30 +0200 [thread overview]
Message-ID: <8735t96qgx.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <62c763ab-2303-85d8-df11-f929a0ef1c0d@linaro.org> (Adhemerval Zanella's message of "Tue, 22 Jun 2021 13:33:57 -0300")
* Adhemerval Zanella:
> Currently, you need to interpose both pthread_create and thrd_create. Florian
> has suggested we allow pthread_create to be interposable (meaning glibc will
> issue a plt call on each usage).
>
> We can do it for clone instead, it would have the advantage to hide
> the multiple architecture different kernel ABIs.
But the clone call is very low-level. The start routine is not called
with a fully configured thread, so wrapping the startup routine would be
rather awkward.
The guts of posix_spawn are equally tricky because code is running
without a properly configured TCB and stack. I'm not sure if it
possible to call an interceptable execve from posix_spawn, for instance.
We would need to know more about interceptor requirements to see if
there is a solution.
Thanks,
Florian
next prev parent reply other threads:[~2021-06-23 6:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 17:55 John Mellor-Crummey
2021-06-17 19:42 ` Adhemerval Zanella
2021-06-17 20:09 ` Florian Weimer
2021-06-17 23:06 ` Adhemerval Zanella
2021-06-23 17:42 ` Ben Woodard
2021-07-30 14:58 ` Adhemerval Zanella
2021-07-30 18:59 ` Ben Woodard
2021-07-30 21:09 ` Adhemerval Zanella
2021-07-31 0:59 ` Ben Woodard
2021-08-04 18:11 ` Adhemerval Zanella
2021-08-05 10:32 ` Szabolcs Nagy
2021-08-05 19:36 ` Ben Woodard
2021-08-06 9:04 ` Szabolcs Nagy
2021-06-21 19:42 ` John Mellor-Crummey
2021-06-22 8:15 ` Florian Weimer
2021-06-22 15:04 ` John Mellor-Crummey
2021-06-22 15:36 ` Florian Weimer
2021-06-22 16:17 ` John Mellor-Crummey
2021-06-22 16:33 ` Adhemerval Zanella
2021-06-23 6:32 ` Florian Weimer [this message]
2021-06-23 20:06 ` Mark Krentel
2021-06-18 17:48 ` John Mellor-Crummey
2021-06-18 18:27 ` Adhemerval Zanella
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=8735t96qgx.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=janderson@rice.edu \
--cc=johnmc@rice.edu \
--cc=krentel@rice.edu \
--cc=libc-alpha@sourceware.org \
--cc=woodard@redhat.com \
--cc=xm13@rice.edu \
/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).