linux-kernel - Re: [PATCH] x86: Find offset for crashkernel reservation automatically

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: <20080627202932.16634031@kopernikus.site>
Date:	Fri, 27 Jun 2008 20:29:32 +0200
From:	Bernhard Walle <bwalle@...e.de>
To:	ebiederm@...ssion.com (Eric W. Biederman)
Cc:	Vivek Goyal <vgoyal@...hat.com>, x86@...nel.org,
	kexec@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86: Find offset for crashkernel reservation
 automatically

* ebiederm@...ssion.com (Eric W. Biederman) [2008-06-27 11:00]:
> Bernhard Walle <bwalle@...e.de> writes:
> 
> > Ah, that's true. Only on x86, right? (That would be an alternative for
> > ia64, too ...)
> >
> > But in general policy should go in userspace (if possible), so I agree
> > with you that kexec-tools can handle that.
> 
> At a quick skim the patch looks good.  I thought I had initially implemented
> the code to work this way but apparently in all of the churn that aspect of it
> got lost.
> 
> Let's start with trying to allocate the memory as low as possible for
> a crash kernel (I think you are already doing that).

Yes, in 95 % of the cases the crashkernel still gets reserved at 16M.



Bernhard
-- 
Bernhard Walle, SUSE LINUX Products GmbH, Architecture Development
--
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/