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]

Date:	Wed, 29 Jul 2009 16:18:57 -0400
From:	Neil Horman <nhorman@...driver.com>
To:	Scott James Remnant <scott@...onical.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 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.

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?
Neil

> Scott
> -- 
> Scott James Remnant
> scott@...onical.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/