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]

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

On 12/16/2010 02:00 AM, Stanislaw Gruszka wrote:
> On Wed, Dec 15, 2010 at 08:29:01PM -0800, Yinghai Lu wrote:
>> please check
>>
>> [PATCH] x86, crashkernel, 32bit: only try to get range under 512M
>>
>> Steanishlaw report kdump is 32bit is broken.
> LOL
> 
>> 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>
> 
> Patch fix problem on my T-60 laptop.
> 
> As expected patch does not help on my other T-500 x86_64 system,
> kdump not work there, but perhaps this is a different problem,
> I'm going to check it.
> 

I think limiting kdump below 512 MiB on 32 bits may make sense; perhaps
even on 64 bits.  It's pretty conservative, after all...

Opinions?

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

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