linux-kernel - Re: [Patch 0/8] V3 Implement crashkernel=auto

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:	Thu, 13 Aug 2009 03:49:24 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Bernhard Walle <bernhard.walle@....de>
Cc:	Amerigo Wang <amwang@...hat.com>, linux-kernel@...r.kernel.org,
	tony.luck@...el.com, linux-ia64@...r.kernel.org,
	Neil Horman <nhorman@...hat.com>,
	Andi Kleen <andi@...stfloor.org>, akpm@...ux-foundation.org,
	Fenghua Yu <fenghua.yu@...el.com>, Ingo Molnar <mingo@...e.hu>,
	Anton Vorontsov <avorontsov@...mvista.com>
Subject: Re: [Patch 0/8] V3 Implement crashkernel=auto

Bernhard Walle <bernhard.walle@....de> writes:

> * Amerigo Wang <amwang@...hat.com> [2009-08-13 10:19]:
>> Sure.
>> 
>> But if we disable CONFIG_KEXEC_AUTO_RESERVE, that means
>> crashkernel=auto will be invalid, this is the same as it is now.
>
> Ok, but since 'crashkernel=auto' is not used today, nobody has
> 'crashkernel=auto' in the bootloader configuration. So I don't see any
> practial advantage of that config option.
>
> Eric, what's your opinion on that, do we need a config option
> CONFIG_KEXEC_AUTO_RESERVE or could we just implement that feature
> unconditionally (if CONFIG_KEXEC is enabled, of course).

The only reason I can see the option going away would be
a dependency on CONFIG_HOTPLUG_MEM.

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/