From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Markus Wichmann <nullplan@gmx.net>
Cc: mtk.manpages@gmail.com, musl@lists.openwall.com,
Carlos O'Donell <carlos@redhat.com>
Subject: Re: [musl] Simple question regarding read-write locks precedence
Date: Tue, 31 Mar 2020 22:15:15 +0200 [thread overview]
Message-ID: <382234b2-27f8-2178-3c89-d719a66b071c@gmail.com> (raw)
In-Reply-To: <20200331194544.GC2683@voyager>
Hi Carlos,
Can you comment on this note about your text[1] in the
pthread_rwlockattr_setkind_np.3 manual page:
On 3/31/20 9:45 PM, Markus Wichmann wrote:
> On Tue, Mar 31, 2020 at 09:02:24PM +0200, Michael Kerrisk (man-pages) wrote:
>> So, is there still something you think needs fixing in the page?
>>
>
> Yes.
>
> |This is ignored by glibc because the POSIX requirement to support
> |recursive writer locks would cause this option to create trivial
> |deadlocks;[...]
>
> There is no POSIX requirement to support recursive writer locks. I think
> this is meant to say "recursive reader locks".
Thanks,
Michael
[1] https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/?id=0d255e74c098dd2ad420367503398ad7f8f82024
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2020-03-31 20:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 15:05 Koen Vandeputte
2020-03-31 15:09 ` Rich Felker
2020-03-31 15:21 ` Koen Vandeputte
2020-03-31 15:26 ` Rich Felker
2020-03-31 17:21 ` Markus Wichmann
2020-03-31 17:37 ` Rich Felker
2020-03-31 18:38 ` Markus Wichmann
2020-03-31 19:02 ` Michael Kerrisk (man-pages)
2020-03-31 19:45 ` Markus Wichmann
2020-03-31 20:15 ` Michael Kerrisk (man-pages) [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=382234b2-27f8-2178-3c89-d719a66b071c@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=carlos@redhat.com \
--cc=musl@lists.openwall.com \
--cc=nullplan@gmx.net \
/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).