| 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: Fri, 07 Aug 2009 23:31:52 +0200 From: Bernhard Walle <bernhard.walle@....de> To: "Eric W. Biederman" <ebiederm@...ssion.com> CC: Amerigo Wang <amwang@...hat.com>, Neil Horman <nhorman@...hat.com>, linux-kernel@...r.kernel.org, tony.luck@...el.com, linux-ia64@...r.kernel.org, akpm@...ux-foundation.org, Ingo Molnar <mingo@...e.hu>, Anton Vorontsov <avorontsov@...mvista.com>, Andi Kleen <andi@...stfloor.org>, Kexec Mailing List <kexec@...ts.infradead.org> Subject: Re: [Patch 0/7] Implement crashkernel=auto Eric W. Biederman schrieb: > > With the current set of crashkernel= options we are asking the > distribution installer to perform magic. Moving as much of this logic > into a normal init script for better maintenance is desirable. Not (necessarily) the installer but the program that configures kdump. system-config-kdump on Red Hat, YaST on SUSE. > Bernhard does that sound useful to you? I don't see any problems. I don't know how much effort is it to free already reserved crashkernel memory, but I guess it's not really complicated. Maybe that "1/32" should be specified on the command line like crashkernel=>>5 (for 1/32*system_memory == system_memory>>5), OTOH I have no real strong opinion. Regards, Bernhard -- 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