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
| ||
|
Message-ID: <20171227124429.GB15255@x1> Date: Wed, 27 Dec 2017 20:44:29 +0800 From: Baoquan He <bhe@...hat.com> To: Borislav Petkov <bp@...en8.de> Cc: Jiri Bohac <jbohac@...e.cz>, Toshi Kani <toshi.kani@....com>, David Airlie <airlied@...ux.ie>, Dave Young <dyoung@...hat.com>, joro@...tes.org, kexec@...ts.infradead.org, linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...hat.com>, "H. Peter Anvin" <hpa@...or.com>, Bjorn Helgaas <bhelgaas@...gle.com>, Thomas Gleixner <tglx@...utronix.de>, yinghai@...nel.org, Vivek Goyal <vgoyal@...hat.com> Subject: Re: [PATCH v2] x86/kexec: Exclude GART aperture from vmcore On 12/27/17 at 01:25pm, Borislav Petkov wrote: > On Wed, Dec 27, 2017 at 03:44:49PM +0800, Baoquan He wrote: > > > yes, instead of crashing the machine (because GART may be initialized in the > > > 2nd kernel, overlapping the 1st kernel memory, which the 2nd kernel with its > > > fake e820 map sees as unused). > > > > > > I'd say this is an improvement. > > > > I don't get what you said. If 'iommu=off' only specified in 1st kernel, > > kdump kernel will think the memory which GART bar pointed as a hole. > > This is incorrect. I don't see the improvement. > > So he says, this memory is unused. Why is that incorrect?!? 'iommu=off' specified in 1st kernel, that region will be normal memory, there could be important kernel data written into the place. While kdump kernel will take that region as a gart aperture, trying to read data from that region will cause error which Jiri originally tried to fix.
Powered by blists - more mailing lists