From: Oleg Nesterov <oleg@redhat.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: "Jovi Zhang" <bookjovi@gmail.com>,
"Pádraig Brady" <P@draigbrady.com>,
dhowells@redhat.com, roland@redhat.com, viro@zeniv.linux.org.uk,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] coredump: fix pipe coredump when core limit is 0
Date: Fri, 26 Aug 2011 16:11:39 +0200 [thread overview]
Message-ID: <20110826141139.GB13620@redhat.com> (raw)
In-Reply-To: <20110825184313.GA29763@hmsreliant.think-freely.org>
On 08/25, Neil Horman wrote:
>
> On Thu, Aug 25, 2011 at 05:57:35PM +0200, Oleg Nesterov wrote:
> > On 08/24, Neil Horman wrote:
> > >
> > > The long and the short of it is, making RLIMIT_CORE == 0 for the ispipe case
> > > skip the core dump, breaks lots of user space expectations
> >
> > Not sure this really makes sense, but perhaps ispipe can skip the dump
> > if RLIMIT_CORE == 0 _and_ the signal was sent from the user-space.
> >
> If you can guarantee that the signal came from user space, yes, that would work
> I imagine.
No, I was wrong.
> alternatively I expect we could modify the kernel thread creation
> routine such that it sets PR_SET_DUMPABLE to zero for all kernel threads
Just curious... why?
Oleg.
next prev parent reply other threads:[~2011-08-26 14:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-21 22:36 [PATCH] coredump: fix pipe coredump when core limit is 0 Neil Horman
2011-08-22 13:23 ` Jovi Zhang
2011-08-22 13:27 ` Oleg Nesterov
2011-08-22 15:32 ` Pádraig Brady
2011-08-22 16:19 ` Oleg Nesterov
2011-08-24 10:14 ` Jovi Zhang
2011-08-24 10:17 ` Jovi Zhang
2011-08-24 11:01 ` Neil Horman
2011-08-25 10:03 ` Pádraig Brady
2011-08-25 10:55 ` Neil Horman
2011-08-26 9:15 ` Pádraig Brady
2011-08-25 15:57 ` Oleg Nesterov
2011-08-25 18:43 ` Neil Horman
2011-08-26 14:11 ` Oleg Nesterov [this message]
2011-08-26 15:39 ` Neil Horman
2011-08-26 9:09 ` Pádraig Brady
2011-08-26 14:10 ` Oleg Nesterov
2011-11-14 5:49 ` Jovi Zhang
2012-07-07 11:35 ` Jovi Zhang
-- strict thread matches above, loose matches on Subject: below --
2011-08-21 11:25 bookjovi
2011-08-21 15:25 ` Oleg Nesterov
2011-08-21 15:57 ` Oleg Nesterov
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=20110826141139.GB13620@redhat.com \
--to=oleg@redhat.com \
--cc=P@draigbrady.com \
--cc=akpm@linux-foundation.org \
--cc=bookjovi@gmail.com \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=roland@redhat.com \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.