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
| ||
|
Date: Thu, 10 Feb 2011 11:04:49 +0800 From: Cong Wang <amwang@...hat.com> To: "Eric W. Biederman" <ebiederm@...ssion.com> CC: Seiji Aguchi <seiji.aguchi@....com>, "hpa@...or.com" <hpa@...or.com>, "andi@...stfloor.org" <andi@...stfloor.org>, "bp@...en8.de" <bp@...en8.de>, "seto.hidetoshi@...fujitsu.com" <seto.hidetoshi@...fujitsu.com>, "gregkh@...e.de" <gregkh@...e.de>, "linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-mm@...ck.org" <linux-mm@...ck.org>, "x86@...nel.org" <x86@...nel.org>, "dle-develop@...ts.sourceforge.net" <dle-develop@...ts.sourceforge.net>, Satoru Moriya <satoru.moriya@....com> Subject: Re: [RFC][PATCH v2] Controlling kexec behaviour when hardware error happened. 于 2011年02月10日 01:07, Eric W. Biederman 写道: > > Is there any reason we can't put logic to decided if we should write > a crashdump in the crashdump userspace? > Doesn't this already provide a choice for the user to decide if he wants a crashdump via sysctl? Except some minor issues pointed by you and Greg, this patch looks fine for me. Thanks. -- 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