| 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: <20080626143832.49948500@halley.suse.de> Date: Thu, 26 Jun 2008 14:38:32 +0200 From: Bernhard Walle <bwalle@...e.de> (by way of Bernhard Walle <bwalle@...e.de>) To: Vivek Goyal <vgoyal@...hat.com> Subject: Re: [PATCH] Remove CONFIG_EXPERIMENTAL from kdump * Vivek Goyal [2008-06-26 08:35]: > > On Thu, Jun 26, 2008 at 10:28:03AM +0200, Bernhard Walle wrote: > > * Andrew Morton [2008-06-26 01:23]: > > > > > > > > config PROC_VMCORE > > > > bool "/proc/vmcore support (EXPERIMENTAL)" > > > > - depends on PROC_FS && EXPERIMENTAL && CRASH_DUMP > > > > + depends on PROC_FS && CRASH_DUMP > > > > default y > > > > help > > > > Exports the dump image of crashed kernel in ELF format. > > > > > > What about powerpc, sh and ia64? > > > > At least for ia64 I wouldn't consider it as experimental. Don't know > > about SH and PPC. But should we mark it as EXPERIMENTAL on all > > platforms only because some "exotic" (at least SH) platforms have kdump > > not very long implemented? > > It has been present long enough on ia64 and ppc64. Only new entry seems > to be SH. I would think of leaving it EXPERIMENTAL only on SH. So, "PROC_FS && (!SH || EXPERIMENTAL) && CRASH_DUMP" ? Bernhard -- Bernhard Walle, SUSE LINUX Products GmbH, Architecture Development -- 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