From: "Ludovic Courtès" <ludo@gnu.org>
To: 64666-done@debbugs.gnu.org
Subject: bug#64666: Nested ‘scm_sigaction_for_thread’ calls lead to deadlock
Date: Sun, 16 Jul 2023 22:06:51 +0200 [thread overview]
Message-ID: <871qh7sjs4.fsf@gnu.org> (raw)
In-Reply-To: <87pm4rsuge.fsf@inria.fr> ("Ludovic Courtès"'s message of "Sun, 16 Jul 2023 18:16:17 +0200")
Ludovic Courtès <ludo@gnu.org> skribis:
> It’s possible for ‘sigaction’ (aka. ‘scm_sigaction_for_thread’) to run
> asyncs, which in turn call ‘scm_sigaction_for_thread’ for the very same
> thread, leading to a deadlock:
Fixed in 85520354a8f5de0366c4ac3eb5403aeb27c9515e.
Ludo’.
prev parent reply other threads:[~2023-07-16 20:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-16 16:16 bug#64666: Nested ‘scm_sigaction_for_thread’ calls lead to deadlock Ludovic Courtès
2023-07-16 20:06 ` Ludovic Courtès [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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871qh7sjs4.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=64666-done@debbugs.gnu.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).