[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Mon, 25 Jan 2021 20:48:18 +0100
From: Florian Weimer <fweimer@...hat.com>
To: Markus Wichmann <nullplan@....net>
Cc: musl@...ts.openwall.com
Subject: Re: insufficient checking in
posix_spawn_file_actions_add{open,dup2}
* Markus Wichmann:
> Adding a getpid vDSO call would require adding the code itself, adding
> the PID to the vvar page (isn't that shared among all processes?), and
> adding support for finding the vDSO function into the libcs. All of that
> for rather dubious performance benefits (or can you name a program that
> was not fast enough because getpid() ran too slowly?)
There's some discussion about this in the context of extensible rseq
support, including userspace donating thread-local data for kernel use
(“KTLS”). Reliable PID/TID/UID caching in userspace and sigprocmask
with a userspace fastpath are potential applications.
Thanks,
Florian
--
Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
