From: Richard Weinberger <richard.weinberger@gmail.com>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: Richard Weinberger via Libc-help <libc-help@sourceware.org>,
linux-man <linux-man@vger.kernel.org>
Subject: Re: Clarification of pthread_cleanup_push() needed
Date: Wed, 22 Apr 2020 00:04:29 +0200 [thread overview]
Message-ID: <CAFLxGvxDd8LBW1RLc4hu-sty1_9q0fB0Uo_QMbQ6j+dKT2QmaQ@mail.gmail.com> (raw)
In-Reply-To: <871rogpld6.fsf@mid.deneb.enyo.de>
On Tue, Apr 21, 2020 at 11:41 PM Florian Weimer <fw@deneb.enyo.de> wrote:
>
> * Richard Weinberger via Libc-help:
>
> > But NPTL implements thread cancellation with signals, if I'm not
> > completely mistaken the cleanup routine will run in signal context
> > then.
>
> Deferred cancellation only occurs in signal context if the
> cancellation is acted upon from within a signal handler. For the
> signal handler case, whether cancellation handlers are restricted to
> async-signal-safe function calls depends on the type of signal (some
> are synchronous, not asynchronous) and what is interrupted by the
> signal (for asynchronous signals).
>
> Asynchronous cancellation has even more constraints than asynchronous
> signal safety, but it is rarely used.
I should have noted that I'm using asynchronous cancellation.
Which constraints are these?
--
Thanks,
//richard
next prev parent reply other threads:[~2020-04-21 22:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 20:35 Richard Weinberger
2020-04-21 21:41 ` Florian Weimer
2020-04-21 22:04 ` Richard Weinberger [this message]
2020-04-21 22:12 ` Florian Weimer
2020-04-21 22:48 ` Richard Weinberger
2020-04-21 23:43 ` Florian Weimer
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=CAFLxGvxDd8LBW1RLc4hu-sty1_9q0fB0Uo_QMbQ6j+dKT2QmaQ@mail.gmail.com \
--to=richard.weinberger@gmail.com \
--cc=fw@deneb.enyo.de \
--cc=libc-help@sourceware.org \
--cc=linux-man@vger.kernel.org \
/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).