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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20101217211301.GK14502@redhat.com>
Date:	Fri, 17 Dec 2010 16:13:01 -0500
From:	Vivek Goyal <vgoyal@...hat.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Yinghai Lu <yinghai@...nel.org>,
	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 12:59:30PM -0800, H. Peter Anvin wrote:
> On 12/17/2010 12:11 PM, Vivek Goyal wrote:
> >>
> >> Can we do this in the meantime, just so we fix the immediate problem?
> > 
> > Peter, kexec-tools on 64bit currently seems to be allowing loding bzImage
> > till 896MB. So I am not too keen it to reduce it to 768MB in kernel just
> > because x86_64 could be booted from even higher addresses and somebody
> > first has to do some auditing and experiments.
> > 
> > IMHO, we should have 768MB limit for 32bit and continue with 896MB limit for
> > 64bit and once somebody makes x86_64 boot from even higher address reliably
> > then we can change both kernel and kexec-tools.
> > 
> 
> If we're splitting by architectures anyway, why not leave 32 bits at 512
> MiB and thus making older crashkernels usable just in case someone has a
> frozen toolset?

If you are more comfortable with 512MB for i386, that's fine with me. I
care more for 64bit at this point of time.

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/