From: Rich Felker <dalias@libc.org>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: Askar Safin <safinaskar@zohomail.com>, musl@lists.openwall.com
Subject: Re: [musl] [bug] Ctrl-Z when process is doing posix_spawn makes the process hard to kill
Date: Sat, 18 Jan 2025 05:23:56 -0500 [thread overview]
Message-ID: <20250118102356.GL10433@brightrain.aerifal.cx> (raw)
In-Reply-To: <87ldv8movu.fsf@mid.deneb.enyo.de>
On Sat, Jan 18, 2025 at 10:51:01AM +0100, Florian Weimer wrote:
> * Askar Safin:
>
> > Thanks a lot for answer!
> >
> > ---- On Fri, 17 Jan 2025 10:37:09 +0400 Rich Felker wrote ---
> > > Note that SIGSTOP, which is not blockable interceptible or ignorable,
> > > can't be handled this way, but the pid has not yet leaked to anything
> > > at this point, so the only way SIGSTOP can be generated is by a badly
> > > behaved program signaling random pids, which is not a case that needs
> > > to be handled gracefully.
> >
> > But what if somebody sends SIGSTOP to whole process group using kill(2)?
>
> I would expect that they send SIGCONT afterwards to the same process
> group, to resume execution of all processes. Doesn't this avoid the
> issue?
I mean if you just want a heuristic fix.. I guess?
But certainly they could send SIGSTOP to the group then SIGCONT only
to the single known process.
Rich
next prev parent reply other threads:[~2025-01-18 10:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 23:14 Askar Safin
2025-01-17 6:37 ` Rich Felker
2025-01-17 6:46 ` Rich Felker
2025-01-17 17:55 ` Askar Safin
2025-01-18 9:51 ` Florian Weimer
2025-01-18 10:23 ` Rich Felker [this message]
2025-01-18 11:13 ` Florian Weimer
2025-01-18 20:58 ` Askar Safin
2025-01-18 11:17 ` Rich Felker
2025-01-18 20:16 ` Markus Wichmann
2025-01-19 3:18 ` Rich Felker
2025-01-18 20:52 ` Askar Safin
2025-01-22 21:45 ` Askar Safin
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=20250118102356.GL10433@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=fw@deneb.enyo.de \
--cc=musl@lists.openwall.com \
--cc=safinaskar@zohomail.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).