From: "Laurent Bercot" <ska-supervision@skarnet.org>
To: Supervision <supervision@list.skarnet.org>
Subject: Re: race condition in killall
Date: Sat, 11 May 2019 19:26:47 +0000 [thread overview]
Message-ID: <emd1fbeeac-3b1e-4a48-bf05-9b677449b9b3@elzian> (raw)
In-Reply-To: <CADQ2Nw8d4HxfTrbPj+PuhzeLSE3Kzz3D_yeSb0DnTkHTBruk1w@mail.gmail.com>
>However, both sysvinit's and BusyBox's kilall5 make a kill(-1,
>SIGSTOP) call before going through the PID list and selectively
>sending the requested signal (and I guess Linux does not deliver
>SIGSTOP to the process that contains the call, or it would be
>pointless), and make a kill(-1, SIGCONT) call when they are done, so
>I'm not sure if there's actually a race condition.
Right, I failed to mention that, sorry. It is true that killall5
doesn't have a real race condition... because it stops the world
before killing a set of processes, and restarts the world afterwards.
This is clearly not something I want to use on systems I manage, even
if it technically accomplishes its goal.
--
Laurent
next prev parent reply other threads:[~2019-05-11 19:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-17 13:25 Update on the progress of slew development Casper Ti. Vector
2019-03-17 14:30 ` Oliver Schad
2019-03-18 14:44 ` Casper Ti. Vector
2019-03-19 12:10 ` Casper Ti. Vector
2019-03-19 12:42 ` Casper Ti. Vector
2019-03-19 15:25 ` Casper Ti. Vector
2019-03-19 15:58 ` Oliver Schad
[not found] ` <20190320051439.GA7636@caspervector>
2019-03-20 5:14 ` Casper Ti. Vector
2019-03-20 11:51 ` Casper Ti. Vector
2019-05-04 6:07 ` Casper Ti. Vector
2019-05-05 1:55 ` race condition in killall sysinit
2019-05-07 14:46 ` Casper Ti. Vector
2019-05-11 18:29 ` Guillermo
2019-05-11 19:26 ` Laurent Bercot [this message]
2019-09-27 17:42 ` Update on the progress of slew development Casper Ti. Vector
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=emd1fbeeac-3b1e-4a48-bf05-9b677449b9b3@elzian \
--to=ska-supervision@skarnet.org \
--cc=supervision@list.skarnet.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 NNTP newsgroup(s).