From: Markus Wichmann <nullplan@gmx.net>
To: musl@lists.openwall.com
Subject: Re: [musl] No such process return value in pthread_getcpuclockid
Date: Mon, 10 Feb 2020 21:23:20 +0100 [thread overview]
Message-ID: <20200210202320.GA3383@voyager> (raw)
In-Reply-To: <14a8dbf3-1382-e61c-3b4e-3a3174dd75b2@bell-sw.com>
On Mon, Feb 10, 2020 at 10:57:22PM +0300, Alexander Scherbatiy wrote:
> I can create a thread, join to it and use the thread id in
> pthread_getcpuclockid function after that.
>
Nope, that's a use after free. Joining a thread has the effect of
invalidating all outstanding pthread_ts for the joined thread.
> The Linux Programmer's Manual has the following errors section: "ESRCH No
> thread with the ID thread could be found."
>
And POSIX says "No errors are defined." I'm guessing POSIX wins.
Use-after-free in this case would be dangerous even if it did not crash.
See, once a thread is joined, the pthread_t is invalidated, but it may
be reused. Another thread may immediately create another thread that
coincidentally allocates the pthread_t in exactly the same place as the
old pthread_t was. Not as coincidental as one might think if both
threads have the same stack and guard size.
Once that has happened, pthread_getcpuclockid (or any other pthread_*
function) will access a different thread than you intended. It is a
logic error to do what you want to do, and crashing is one of the best
things that can happen to you if you try. The other possibility is a
really subtle bug that only occurs sometimes. Happy debugging!
> Does pthread_getcpuclockid function from musl follows the similar errors
> handling approach?
>
Musl's pthread_getcpuclockid() cannot fail at this time. It can only
succeed or crash.
Ciao,
Markus
prev parent reply other threads:[~2020-02-10 20:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 19:29 Alexander Scherbatiy
2020-02-10 19:34 ` Rich Felker
2020-02-10 19:57 ` Alexander Scherbatiy
2020-02-10 20:14 ` Rich Felker
2020-02-11 9:16 ` Alexander Scherbatiy
2020-02-10 20:23 ` Markus Wichmann [this message]
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=20200210202320.GA3383@voyager \
--to=nullplan@gmx.net \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).