[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1947568343c.4b19ad8c16088.1387564150395328587@zohomail.com>
Date: Fri, 17 Jan 2025 21:55:50 +0400
From: Askar Safin <safinaskar@...omail.com>
To: "Rich Felker" <dalias@...c.org>
Cc: "musl" <musl@...ts.openwall.com>
Subject: Re: [bug] Ctrl-Z when process is doing posix_spawn makes the
process hard to kill
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)?
The bug is not reproducible with fork. Maybe this is kernel bug and should be
forwarded there instead?
--
Askar Safin
https://types.pl/@safinaskar
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
