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: Tue, 11 Feb 2020 12:16:18 +0300 [thread overview]
Message-ID: <54047ebd-8711-1e54-e0d3-e4609cc477c7@bell-sw.com> (raw)
In-Reply-To: <20200210201448.GS1663@brightrain.aerifal.cx>
On 10.02.2020 23:14, Rich Felker wrote:
> The specification of ESRCH for pthread interfaces was a bug, because a
> "shall fail" or even "may fail" condition makes no sense with a
> behavior that's explicitly undefined (in which case the implementation
> is allowed to do anything at all). This was clarified in POSIX 2008 as
> a result of Austin Group interpretation 142:
>
> https://collaboration.opengroup.org/austin/interps/documents/14366/AI-142.txt
Thank you. It sounds right that If an application attempts to use a
thread ID whose lifetime has ended, the behavior is undefined.
I see that "POSIX 2008 as a result of Austin Group interpretation 142"
has strange comment about pthread_getcpuclockid() function:
"The same argument applies to the ESRCH errors for pthread_detach(),
pthread_getschedparam(), pthread_setschedparam() and
pthread_setschedprio().
(It does not apply to pthread_getcpuclockid() since the function
could just always return a fixed clock ID without needing to examine
the thread ID.)"
What does it mean that pthread_getcpuclockid() does not need to
examine the thread ID? As I see from the musl pthread_getcpuclockid()
implementation it really uses the thread ID:
https://git.musl-libc.org/cgit/musl/tree/src/thread/pthread_getcpuclockid.c
Thanks,
Alexander.
>
> Unfortunately the Linux man pages have not corrected this.
>
> Rich
next prev parent reply other threads:[~2020-02-11 9:16 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 [this message]
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=54047ebd-8711-1e54-e0d3-e4609cc477c7@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).