linux-kernel - x86_64/kdump crashkernel reservation breakage in 2.6.31-rc

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>] [day] [month] [year] [list]

Message-ID: <20090615235145.GD30071@sequoia.sous-sol.org>
Date:	Mon, 15 Jun 2009 16:51:45 -0700
From:	Chris Wright <chrisw@...s-sol.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	linux-kernel@...r.kernel.org
Subject: x86_64/kdump crashkernel reservation breakage in 2.6.31-rc

I hesitate to label this a regression since 2.6.30, but at least user
visible change since 2.6.30 that at a minimum needs some docs updates.

The commit "ceefccc: x86: default CONFIG_PHYSICAL_START and
CONFIG_PHYSICAL_ALIGN to 16 MB" has a side effect for kdump users.
The problem is a little convoluted because the typical setup for kdump
includes:

crashkernel=64M@16M or crashkernel=128M@16M

These uses don't account for a relocatable kernel which could omit the
@X location specifier, but it's the typical documented method[1][2][3].

Trouble is, now the original kernel loads at 16MB since it's alignment
request will push it up from the old default of 2MB, and the existing
attempt to reserve a region for the crashkernel will fail.

I think the docs are the problem here, in that they don't adequately
prepare a user for the (now common) relocatable kernel case.
Alternatively, back out the CONFIG_PHYSICAL_ALIGN change...

Thoughts?

thanks,
-chris

[1] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/kdump/kdump.txt;hb=HEAD#l271
[2] http://fedoraproject.org/wiki/Kernel/kdump
[3] http://kbase.redhat.com/faq/docs/DOC-6039
--
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/