linux-kernel - Re: [PATCH] kdump: do not drop entire e820 in crash kernel

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

Message-ID: <510F3E93.9080708@zytor.com>
Date:	Sun, 03 Feb 2013 20:52:35 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Cliff Wickman <cpw@....com>
CC:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...nel.org>,
	kexec@...ts.infradead.org
Subject: Re: [PATCH] kdump: do not drop entire e820 in crash kernel

On 02/03/2013 08:04 PM, Cliff Wickman wrote:
> From: Cliff Wickman <cpw@....com>
>
> The crash kernel is not able to find its root device if that device is not
> on PCI 0.
>
> This is because it is booted with the command line option memmap=exactmap
> which currently clears the e820 table.  So ACPI processing does not
> find reserved i/o spaces.
>
> This works for a device on PCI 0 because ACPI falls back to a legacy mode.
> But the error message " [Firmware Bug]: PCI: MMCONFIG at
>   [mem 0x80000000-0x80cfffff] not reserved in ACPI motherboard resources"
> is written to the log even in this functioning case.
>
> It fails for some devices on UV2, and only for UV2, because SGI seems to
> be the only manufacturer currently using the extended PCI(>0).
>
> The fix is to not drop the entire e820 table on a memmap=exactmap, but
> to preserve all the non-E820_RAM reservations that the BIOS has made.
>

NAK.  This is a fundamntal semantic change to  something that isn't just 
affecting kexec.

This ultimately is the result of the very bad design decision to use the 
command line to muck with the target kernel memory map.

The work is underway to fix this, but this is not the right fix.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

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