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: Sun, 09 Sep 2007 15:06:55 -0600 From: ebiederm@...ssion.com (Eric W. Biederman) To: Bernhard Walle <bwalle@...e.de> Cc: Yinghai Lu <yhlu.kernel@...il.com>, Vivek Goyal <vgoyal@...ibm.com>, linux-arch@...r.kernel.org, discuss@...-64.org, kexec@...ts.infradead.org, linux-kernel@...r.kernel.org Subject: Re: [discuss] [patch 3/5] Use extended crashkernel command line on x86_64 Bernhard Walle <bwalle@...e.de> writes: > * Yinghai Lu <yhlu.kernel@...il.com> [2007-09-09 19:27]: >> > >> > +#ifdef CONFIG_KEXEC >> ... >> >> CONFIG_KEXEC or CONFIG_CRASH_DUMP? > > Good question. The crashkernel parameter was CONFIG_KEXEC before, and > I also wondered why, but I didn't change this because maybe there's > some reason I don't know. > > Vivek, do you know why this was CONFIG_KEXEC? Probably because you use it in the primary kernel you use it. The option reserves an area of memory for the kernel we switch to on panic or another kernel crash. Generally CONFIG_CRASH_DUMP seems to be about the options needed to read out the crash dump after the fact. Eric - 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