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]

Date:	Fri, 27 Jun 2008 11:00:44 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Bernhard Walle <bwalle@...e.de>
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

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).

If we need something more we can add another meta character to specify a limit.
/sbin/kexec should balk at loading if the reserved region is too high.

Ramdisks in particular are a problem because they need to be in low mem.

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