From: Laurent Bercot <ska-dietlibc@skarnet.org>
To: musl@lists.openwall.com
Subject: Re: abort() fails to terminate PID 1 process
Date: Sun, 3 Jul 2016 22:20:46 +0200 [thread overview]
Message-ID: <4f7df3fa-ed15-5650-b26f-47c5225bfbf3@skarnet.org> (raw)
In-Reply-To: <20160703200125.GJ15995@brightrain.aerifal.cx>
On 03/07/2016 22:01, Rich Felker wrote:
> No. Halting the system safely (which kernel panic does) is completely
> different from runaway wrong-code execution, and the only reason we
> don't have runaway wrong-code execution right now is because I built
> in the for(;;) safety in case termination failed.
Halting the system, no matter how safely, is also completely different from
cleanly terminating the aborting process (while not impacting other processes
as is supposed to be guaranteed by Unix). At this point, we're wildly outside
the realm of specification anyway, and I find it acceptable to say that pid 1
abort (or any kind of death for that matter) is UB. Your choice of
implementation for abort() is good and safe, but I think it's just QoI,
not something you're bound to do by a standard.
--
Laurent
next prev parent reply other threads:[~2016-07-03 20:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-18 20:32 Karl Böhlmark
2016-06-19 1:20 ` nathan
2016-06-20 9:02 ` Igmar Palsenberg
2016-06-20 10:04 ` Szabolcs Nagy
2016-06-20 12:00 ` Igmar Palsenberg
2016-06-20 19:41 ` Rich Felker
2016-07-03 10:43 ` Igmar Palsenberg
2016-07-03 13:58 ` Rich Felker
2016-07-03 19:58 ` Laurent Bercot
2016-07-03 20:01 ` Rich Felker
2016-07-03 20:20 ` Laurent Bercot [this message]
2016-07-03 20:24 ` Rich Felker
2016-07-04 13:38 ` Igmar Palsenberg
2016-07-04 13:37 ` Igmar Palsenberg
2016-07-05 3:07 ` Rich Felker
2016-07-30 21:24 ` Igmar Palsenberg
2016-06-20 10:29 ` Natanael Copa
2016-07-03 22:03 ` Rich Felker
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=4f7df3fa-ed15-5650-b26f-47c5225bfbf3@skarnet.org \
--to=ska-dietlibc@skarnet.org \
--cc=musl@lists.openwall.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).