linux-kernel - Re: [PATCH] coredump: fix pipe coredump when core limit is 0

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110826141139.GB13620@redhat.com>
Date:	Fri, 26 Aug 2011 16:11:39 +0200
From:	Oleg Nesterov <oleg@...hat.com>
To:	Neil Horman <nhorman@...driver.com>
Cc:	Jovi Zhang <bookjovi@...il.com>,
	Pádraig Brady <P@...igbrady.com>,
	dhowells@...hat.com, roland@...hat.com, viro@...iv.linux.org.uk,
	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] coredump: fix pipe coredump when core limit is 0

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.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/