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:	Fri, 17 Dec 2010 14:50:35 -0500
From:	Vivek Goyal <vgoyal@...hat.com>
To:	Yinghai Lu <yinghai@...nel.org>
Cc:	"H. Peter Anvin" <hpa@...or.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 Fri, Dec 17, 2010 at 11:46:08AM -0800, Yinghai Lu wrote:
> On 12/17/2010 11:39 AM, H. Peter Anvin wrote:
> > On 12/17/2010 10:21 AM, Yinghai Lu wrote:
> >>>>
> >>>> Do we have actual testing for how high the 64-bit kernel will load?
> >>>
> >>> I will do some experiments on my box today and let you know.
> >>
> >> if bzImage is used, it is 896M.
> >>
> > 
> > Why?  896 MiB is a 32-bit kernel limitation which doesn't have anything
> > to do with the bzImage format.
> > 
> > So unless there is something going on here, I suspect you're just plain
> > flat wrong.
> 
> kexec-tools have some checking when it loads bzImage.
> 

Yinghai,

I think x86_64 might have just inherited the settings of 32bit without
giving it too much of thought. At that point of time nobody bothered
to load the kernel from high addresses. So these might be artificial
limits.

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