From: Daniel Jacobowitz <dan@debian.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: phil-list@redhat.com, Linus Torvalds <torvalds@transmeta.com>,
Alexander Viro <viro@math.psu.edu>,
S Vamsikrishna <vamsi_krishna@in.ibm.com>,
Mark Gross <markgross@thegnar.org>,
Ulrich Drepper <drepper@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch] thread-aware coredumps, 2.5.43-C3
Date: Mon, 21 Oct 2002 10:54:32 -0400 [thread overview]
Message-ID: <20021021145432.GA22470@nevyn.them.org> (raw)
In-Reply-To: <1035210573.28189.127.camel@irongate.swansea.linux.org.uk>
On Mon, Oct 21, 2002 at 03:29:33PM +0100, Alan Cox wrote:
> On Thu, 2002-10-17 at 17:40, Daniel Jacobowitz wrote:
> > My only problem with this is that you're waiting for all threads by
> > SIGKILLing them. If a process vforks or clones, and then the child
> > crashes, the parent will receive a SIGKILL - iff we are dumping core.
> > That's a change in behavior that seems a bit too arbitrary to me.
>
> It also has a security impact when you construct a fork/fork/crash
> sequence that sends sigkill to the module loader or a kernel thread
> during start up that has not yet dropped its association with the user
> code.
Why? It's not like userspace couldn't send that SIGKILL on its own,
right? If it's still killable it had better be safe to do so.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-10-21 14:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-08 12:09 [patch] thread-aware coredumps part 1, tcore-2.5.41-A6 Ingo Molnar
2002-10-08 13:30 ` mgross
2002-10-17 9:11 ` [patch] thread-aware coredumps, 2.5.43-C3 Ingo Molnar
2002-10-17 16:40 ` Daniel Jacobowitz
2002-10-21 14:29 ` Alan Cox
2002-10-21 14:54 ` Daniel Jacobowitz [this message]
2002-10-21 16:16 ` Alan Cox
2002-10-21 16:04 ` Daniel Jacobowitz
2002-10-17 21:07 ` mgross
2002-10-18 0:48 ` Daniel Jacobowitz
2002-10-18 13:57 ` Mark Gross
2002-10-18 14:03 ` Mark Gross
2002-10-19 13:26 ` Mark Kettenis
2002-10-19 19:26 ` Bill Davidsen
2002-10-19 19:34 ` Ulrich Drepper
2002-10-19 13:20 ` Mark Kettenis
2002-10-19 18:42 ` Mark Gross
2002-10-18 1:10 ` Andi Kleen
2002-10-18 1:35 ` Mark Gross
2002-10-18 2:12 ` Andi Kleen
2002-10-18 2:58 ` Mark Gross
2002-10-18 3:55 ` Daniel Jacobowitz
2002-10-18 14:00 ` mgross
2002-10-21 15:17 ` Pavel Machek
2002-11-03 7:32 ` Ulrich Drepper
2002-10-19 17:32 ` Ulrich Drepper
2002-10-18 2:23 ` Ulrich Drepper
2002-10-18 2:40 ` Andi Kleen
2002-10-08 18:04 ` [patch] thread-aware coredumps part 1, tcore-2.5.41-A6 mgross
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=20021021145432.GA22470@nevyn.them.org \
--to=dan@debian.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@thegnar.org \
--cc=phil-list@redhat.com \
--cc=torvalds@transmeta.com \
--cc=vamsi_krishna@in.ibm.com \
--cc=viro@math.psu.edu \
/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).