From: Carlos O'Donell <carlos@redhat.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
linux-man <linux-man@vger.kernel.org>,
libc-alpha <libc-alpha@sourceware.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: Re: [patch] Describe issues with cancellation points in signal handlers.
Date: Sun, 6 Oct 2019 22:17:29 -0400 [thread overview]
Message-ID: <e9f8e552-1b23-b54e-cfb3-b1b2cb715e09@redhat.com> (raw)
In-Reply-To: <165a5e50-6c0f-7464-44ae-e74ac10a6e55@gmail.com>
On 10/5/19 7:48 AM, Michael Kerrisk (man-pages) wrote:
> Hello Carlos,
>
> On 10/5/19 12:12 AM, Carlos O'Donell wrote:
>> In a recent conversation with Mathieu Desnoyers I was reminded
>> that we haven't written up anything about how deferred cancellation
>> and asynchronous signal handlers interact. Mathieu ran into some
>> of this behaviour and I promised to improve the documentation in
>> this area to point out the potential pitfall.
>>
>> Thoughts?
>
> I've applied this. If some review comments come it, I can
> tweak the text.
>
> Thanks!
Thank you! I tried hard to keep the "asynchronous signal" and
"deferred cancellation" terms all consistent. It's all a bit of
a mouthful, so I'd be happy if we could have come up with simpler
language, but it's hard to write it any simpler without loosing
the exactitude of what I'm trying to say. I'm happy to see future
edits that simplify the language. At the very least we now say
something about this corner case so people aren't caught off guard.
--
Cheers,
Carlos.
prev parent reply other threads:[~2019-10-07 2:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 21:12 [patch] Describe issues with cancellation points in signal handlers Carlos O'Donell
2019-10-05 11:48 ` Michael Kerrisk (man-pages)
2019-10-07 2:17 ` Carlos O'Donell [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=e9f8e552-1b23-b54e-cfb3-b1b2cb715e09@redhat.com \
--to=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--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 NNTP newsgroup(s).