From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: abort() fails to terminate PID 1 process
Date: Sun, 3 Jul 2016 16:01:25 -0400 [thread overview]
Message-ID: <20160703200125.GJ15995@brightrain.aerifal.cx> (raw)
In-Reply-To: <82c4150b-3433-4e3f-2304-9aceef82a54b@skarnet.org>
On Sun, Jul 03, 2016 at 09:58:45PM +0200, Laurent Bercot wrote:
> On 03/07/2016 15:58, Rich Felker wrote:
> >Whether you realize it or not, what you're saying is equivalent to
> >saying that it's UB for a process that runs as pid 1 to call abort().
> >There is no basis for such a claim.
>
> There's no basis in the specification, but in practice, on Linux at least,
> a process that runs as pid 1 outside of a container and that exits - whether
> normally or via abort() or anything else - will cause a kernel panic. So
> treating that case as UB is defensible, at least until musl is ported to an
> OS where pid 1 death is less dramatic.
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.
Rich
next prev parent reply other threads:[~2016-07-03 20:01 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 [this message]
2016-07-03 20:20 ` Laurent Bercot
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=20160703200125.GJ15995@brightrain.aerifal.cx \
--to=dalias@libc.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).