linux-kernel - Re: [PATCH] exec: Make do_coredump more robust and safer when using pipes in core

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: <20090801134146.GA19910@localhost.localdomain>
Date:	Sat, 1 Aug 2009 09:41:46 -0400
From:	Neil Horman <nhorman@...driver.com>
To:	Scott James Remnant <scott@...ntu.com>
Cc:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	earl_chew@...lent.com
Subject: Re: [PATCH] exec: Make do_coredump more robust and safer when
	using pipes in core_pattern

On Fri, Jul 31, 2009 at 09:20:10PM +0100, Scott James Remnant wrote:
> On Wed, 2009-07-29 at 16:18 -0400, Neil Horman wrote:
> 
> > On Wed, Jul 29, 2009 at 04:13:02PM +0100, Scott James Remnant wrote:
> > > On Mon, 2009-06-22 at 13:28 -0400, Neil Horman wrote:
> > > 
> > > > 2) Allow for the kernel to wait for a core_pattern process to complete.  One of
> > > > the things core_pattern processes might do is interrogate the status of a
> > > > crashing process via its /proc/pid directory.  To ensure that that directory is
> > > > not removed prematurely, we wait for the process to exit prior to cleaning it
> > > > up.
> > > > 
> > > Would this mean that the kernel would wait for the pattern process to
> > > complete before PANIC in the case of init core dumping?
> > > 
> > > I'd find that useful :-)
> > > 
> > Not without additional work.  If init crashed in the initramfs, I don't think
> > theres a way to handle that.  If it crashes at some later time, I think it just
> > gets restarted IIRC.  I'm sure you can change that behavior, but this patch
> > doesn't address that.
> > 
> When the system init daemon crashes, the kernel PANICs.  When not using
> core_pattern, this is ok, we get a core file - when using apport, as far
> as I can tell it never waits for apport to finish so we don't get the
> crash.
> 
This is non-sensical.  If init crashes, and the kernel panics, you'll only get a
core by sheer luck and good fortune.  The kernels paniced, theres no
serialization between the halting/rebooting of cpus and the completion of a core
dump operation, be it to a pipe or disk.

> I was hoping that by waiting for the core_pattern process to finish,
> this might solve this issue.
> 
See above, some of it might work, but if the kernel is going to panic, theres no
way to fork another process, let alone wait for it to finish, at least not with
any level of reliability.

> The other obvious fix I can apply to the init daemon is to reset the
> core pattern and deliberately dump core somewhere that can be picked up.
> 
how are you getting this core if the system is actually panic'ed?  Or is
something else actually happening.

> > If you want to debug a custom init process, why not run a wrapper program as
> > init, that just forks the init you want to run and captures the core when it
> > crashes?
> > 
> Because then that's not the init daemon; it's not pid 1, it doesn't have
> processes reparented to it.  And it's very annoying having the entire
> system reparented to gdb, which doesn't deal so well with that ;-)
> 

You're not by any chance talking about an init crash that results in a respawn
are you?  That doesn't result in a panic, and would allow for a crash to
complete.  If thats the case, then core_pattern might just work (I admit to not
having tried it).

Neil

> Scott
> -- 
> Scott James Remnant
> scott@...ntu.com


--
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/