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
| ||
|
Message-ID: <20121213122048.GF5246@sergelap> Date: Thu, 13 Dec 2012 06:20:48 -0600 From: Serge Hallyn <serge.hallyn@...onical.com> To: Neil Horman <nhorman@...driver.com> Cc: linux-kernel@...r.kernel.org, Daniel Berrange <berrange@...hat.com>, Alexander Viro <viro@...iv.linux.org.uk>, Andrew Morton <akpm@...ux-foundation.org>, containers@...ts.linux-foundation.org Subject: Re: [PATCH] core_pattern: set core helpers root and namespace to crashing process Quoting Neil Horman (nhorman@...driver.com): > Theres one problem I currently see with it, and that is that I'm not sure we can > change the current behavior of how the root fs is set for the pipe reader, lest > we break some user space expectations. As such, I've added a sysctl in this > patch to allow administrators to globally select if a core reader specified via > /proc/sys/kernel/core_pattern should use the global rootfs, or the (possibly) > chrooted fs of the crashing process. Practical question: How is the admin to make an educated decision on how to set the sysctl? -serge -- 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/
Powered by blists - more mailing lists