linux-kernel - Re: kdump broken on 2.6.37-rc4

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: <4D0AE231.4010804@zytor.com>
Date:	Thu, 16 Dec 2010 20:08:17 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Yinghai <yinghai@...nel.org>
CC:	Vivek Goyal <vgoyal@...hat.com>,
	Stanislaw Gruszka <sgruszka@...hat.com>,
	Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	Maxim Uvarov <muvarov@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Neil Horman <nhorman@...hat.com>
Subject: Re: kdump broken on 2.6.37-rc4

On 12/16/2010 07:58 PM, Yinghai wrote:
> Please don't do that to 64 bit
> 
> My big system with 1024g memory and a lot of cards with rhel 6 to make kdump work must have crashkernel=512m and second kernel need to take pci=nomsi
> 
> Thanks
> 

Hm, this seems like an epic FAIL.

First of all, the current code still limits it to 896 MiB, so 512 MiB is
not a significant restriction.

Second, this patch only applies if "crashkernel=" is not specified, so
it doesn't even apply to your situation.

Third, if you have to specify "crashkernel=" that means that there is
yet another problem here that should be fixed.

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