From: Florian Weimer <fweimer@redhat.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: linux-toolchains@vger.kernel.org
Subject: Re: Fw: [isocpp-parallel] WG14 n3917 - Program termination in the presence of multiple threads
Date: Tue, 14 Jul 2026 22:16:27 +0200 [thread overview]
Message-ID: <lhuy0fdqqck.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <3dd4c609-b7db-4769-a3d0-1bbdff088bc0@paulmck-laptop> (Paul E. McKenney's message of "Tue, 14 Jul 2026 10:58:59 -0700")
* Paul E. McKenney:
> Just FYI. Unless I am missing something, this would not affect the
> Linux kernel. But I could be missing something...
This seems to require new behavior?
* SYS_tkill and SYS_tgkill with signal SIGABRT terminate the current
thread or a group of threads abnormally
The proposal is a bit weird to me. It seems to discourage using an
atexit handler to shut down a service thread (by synchronizing with it).
Thanks,
Florian
prev parent reply other threads:[~2026-07-14 20:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 17:58 Fw: [isocpp-parallel] WG14 n3917 - Program termination in the presence of multiple threads Paul E. McKenney
2026-07-14 20:16 ` 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=lhuy0fdqqck.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=linux-toolchains@vger.kernel.org \
--cc=paulmck@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