linux-kernel - Re: [PATCH v2] Do not reserve crashkernel high memory if crashkernel low memory reserving failed

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]

Message-ID: <20150721073814.GA17513@gmail.com>
Date:	Tue, 21 Jul 2015 09:38:14 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Dave Young <dyoung@...hat.com>
Cc:	Baoquan He <bhe@...hat.com>, tglx@...utronix.de, mingo@...hat.com,
	hpa@...or.com, bp@...e.de, akpm@...ux-foundation.org,
	jkosina@...e.cz, vgoyal@...hat.com, linux-kernel@...r.kernel.org,
	yinghai@...nel.org, Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [PATCH v2] Do not reserve crashkernel high memory if crashkernel
 low memory reserving failed


* Dave Young <dyoung@...hat.com> wrote:

> Hi, Baoquan
> 
> The interface was introduced by Yinghai, ccing him.

Also, why was this syntax introduced in the first place? Why should the user 
care??

We should only have a single crashkernel option, to enable it - and everything 
else should be figured out by the kernel, automatically.

Any other sub-options just paper over some fragility elsewhere and make the 
feature harder to use, hence more fragile.

Thanks,

	Ingo
--
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/