From: Szabolcs Nagy <nsz@port70.net>
To: Hydro Flask <hydroflask@yqxmail.com>
Cc: Florian Weimer <fweimer@redhat.com>, musl@lists.openwall.com
Subject: Re: [musl] Idea: futex() system call entry point
Date: Fri, 17 Jul 2020 11:21:11 +0200 [thread overview]
Message-ID: <20200717092111.GA3210874@port70.net> (raw)
In-Reply-To: <4095a8a7f75becee9bcfc71024e43802@yqxmail.com>
* Hydro Flask <hydroflask@yqxmail.com> [2020-07-16 23:29:53 -0700]:
> On 2020-07-16 23:10, Florian Weimer wrote:
> > * Hydro Flask:
> >
> > > I have a project that implements an API that must be AS-safe.
> >
> > > Had the idea of using futex() but my other constraint is that the
> > > blocking call must also be a cancellation point.
> >
> > Cancellation points in signal handlers lead to asynchronous
> > cancellation. Are you sure that this is what you want?
>
> Yes I am aware of that. The caller is responsible for making sure it is safe
> to call the cancellation point in the signal handler per the recommendations
> in POSIX.
how does the caller ensure that the interrupted
code is async cancel safe?
>
> This same API is used in both synchronous and asynchronous contexts, which
> is why it must be a cancellation point.
next prev parent reply other threads:[~2020-07-17 9:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 5:51 Hydro Flask
2020-07-17 6:10 ` Florian Weimer
2020-07-17 6:29 ` Hydro Flask
2020-07-17 9:21 ` Szabolcs Nagy [this message]
2020-07-17 14:43 ` Carlos O'Donell
2020-07-17 18:57 ` Hydro Flask
2020-07-17 21:10 ` Szabolcs Nagy
2020-07-17 21:19 ` Rich Felker
2020-07-17 21:27 ` Carlos O'Donell
2020-07-17 21:37 ` Hydro Flask
2020-07-17 23:30 ` Rich Felker
2020-07-18 1:21 ` Hydro Flask
2020-07-18 7:56 ` Szabolcs Nagy
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=20200717092111.GA3210874@port70.net \
--to=nsz@port70.net \
--cc=fweimer@redhat.com \
--cc=hydroflask@yqxmail.com \
--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).