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, 16 Dec 2010 19:58:48 -0800
From:	Yinghai <yinghai@...nel.org>
To:	"H. Peter Anvin" <hpa@...or.com>
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

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

On Dec 16, 2010, at 7:31 PM, "H. Peter Anvin" <hpa@...or.com> wrote:

> On 12/15/2010 08:29 PM, Yinghai Lu wrote:
>> please check
>> 
>> [PATCH] x86, crashkernel, 32bit: only try to get range under 512M
>> 
>> Steanishlaw report kdump is 32bit is broken.
>> 
>> in misc.c for decompresser, it will do sanity checking to make sure heap
>> heap under 512M.
>> 
>> So limit it in first kernel under 512M for 32bit system.
>> 
>> Reported-by: Stanislaw Gruszka <sgruszka@...hat.com>
>> Signed-off-by: Yinghai Lu <yinghai@...nel.org>
>> 
>> ---
>> arch/x86/kernel/setup.c |   14 +++++++++++++-
>> 1 file changed, 13 insertions(+), 1 deletion(-)
>> 
> 
> I'd like to apply a modified version of this patch (attached.)
> 
> Ack/nak, people?
> 
>    -hpa
> <0001-x86-kexec-Limit-the-crashkernel-address-to-512-MiB.patch>
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ