From: Florian Weimer <fweimer@redhat.com>
To: Michael Kerrisk <mtk.manpages@gmail.com>
Cc: "libc-alpha\@sourceware.org" <libc-alpha@sourceware.org>
Subject: Re: [PATCH v2] manual: Add pthread_attr_setsigmask_np, pthread_attr_getsigmask_np
Date: Wed, 03 Jun 2020 14:24:24 +0200 [thread overview]
Message-ID: <87zh9kwd53.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <CALxWeYrXvp3SAYrt9-Yi6b4=d5E4N-QR3UnkPrQ+rysWcQzrMw@mail.gmail.com> (Michael Kerrisk's message of "Wed, 3 Jun 2020 14:15:09 +0200")
* Michael Kerrisk:
>> > +It is possible to create a new thread with a specific signal mask
>> > +without using these functions. On the thread that calls
>
> [I missed this piece, that the bullet list is *steps in the thread
> that calls pthread_create()*. Sorry about the confusion.
In the HTML version, it's quite visible: the macro description is
indented. Likewise in the Info version. So I think we are good.
>> > +@code{pthread_create}, the required steps for the general case are:
>> > +
>> > +@enumerate 1
>> > +@item
>> > +Mask all signals, and save the old signal mask, using
>> > +@code{pthread_sigmask}. This ensures that the new thread will be
>> > +created with all signals masked, so that signals can arrive on the
>>
>> s/signals/no signals/
>>
>> The word "arrive" seems a bit vague to me. How about:
>>
>> [[
>> This ensures that the new thread will be created with all signals
>> masked, so that no signals can be delivered until the desired signal
>> mask is set.
>> ]]
Thanks for keeping my terminology straight. Yes, “delivered” is indeed
the term I was looking for.
Florian
prev parent reply other threads:[~2020-06-03 12:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 9:30 Florian Weimer
2020-06-03 10:10 ` Michael Kerrisk (man-pages)
2020-06-03 12:15 ` Michael Kerrisk
2020-06-03 12:24 ` Florian Weimer [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=87zh9kwd53.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=mtk.manpages@gmail.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).