[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160705030738.GS15995@brightrain.aerifal.cx>
Date: Mon, 4 Jul 2016 23:07:38 -0400
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: abort() fails to terminate PID 1 process
On Mon, Jul 04, 2016 at 03:37:35PM +0200, Igmar Palsenberg 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.
> >
> > A vague "pid 1 is special" rule (which the standard does not support
> > except in a few very specific places where an implementation-defined
> > set of processes are permitted to be treated in specific special ways)
> > does not imply "calling a function whose behavior is well-defined can
> > legitimately lead to runaway code execution if the pid is 1".
>
> But doesn't "bevavior is well-defined" also imply that that function
> behaves as it should ? If it doesn't, doesn't the "well-defined" no longer
> apply ? I call it UB in this case.
"Behavior is well-defined" means the specification tells what it does
and does not leave it implementation-defined, unspecified, or
undefined -- neither by explicitly saying so, nor by omission.
> The standard also says a process can't ignore a SIGKILL, but on pid 1, it
> has no effect. I pretty much call that UB myself.
You keep using that word. I do not think it means what you think it
means.
If anything what you're arguing is that the Linux kernel has a bug,
since the behavior of raising SIGKILL is specified and Linux does not
do what the spec says (for pid 1). That does not mean it's undefined
but rather that the implementation is behaving contrary to the defined
behavior.
Rich
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.
