From: Alexander Scherbatiy <alexander.scherbatiy@bell-sw.com>
To: musl@lists.openwall.com, Rich Felker <dalias@libc.org>
Subject: Re: [musl] No such process return value in pthread_getcpuclockid
Date: Mon, 10 Feb 2020 22:57:22 +0300 [thread overview]
Message-ID: <14a8dbf3-1382-e61c-3b4e-3a3174dd75b2@bell-sw.com> (raw)
In-Reply-To: <20200210193427.GR1663@brightrain.aerifal.cx>
On 10.02.2020 22:34, Rich Felker wrote:
> On Mon, Feb 10, 2020 at 10:29:02PM +0300, Alexander Scherbatiy wrote:
>> Hello,
>>
>> It seems that pthread_getcpuclockid does not properly handle non
>> valid thread id argument.
>>
>> Below is a sample which calls pthread_getcpuclockid with NULL thread
>> id. The expected result is ESRCH (No thread with the ID thread could
>> be found). It crashes in my docker with Alpine Linux 3.11.3 (musl
>> libc x86_64 1.1.24). It returns ESRCH on my Ubuntu system.
> There's no such thing as a "null thread id". A pthread_t value is
> either the id of a thread which is still valid (still running or
> joinable and not yet joined), or *any* use of it produces undefined
> behavior. There is no value reserved for a sentinel. If you need an
> optional thread id variable/field, you need a separate validity flag
> alongside it.
>
> None of this is unique to musl; it's the way the POSIX threads
> interfaces are designed.
I can create a thread, join to it and use the thread id in
pthread_getcpuclockid function after that.
The Linux Programmer's Manual has the following errors section: "ESRCH
No thread with the ID thread could be found."
Does pthread_getcpuclockid function from musl follows the similar errors
handling approach?
Thanks,
Alexandr.
>
> Rich
next prev parent reply other threads:[~2020-02-10 19:57 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 [this message]
2020-02-10 20:14 ` Rich Felker
2020-02-11 9:16 ` Alexander Scherbatiy
2020-02-10 20:23 ` Markus Wichmann
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=14a8dbf3-1382-e61c-3b4e-3a3174dd75b2@bell-sw.com \
--to=alexander.scherbatiy@bell-sw.com \
--cc=dalias@libc.org \
--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).