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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 30 Aug 2018 22:13:49 +0800 From: Baoquan He <bhe@...hat.com> To: "Kirill A. Shutemov" <kirill@...temov.name> Cc: x86@...nel.org, kexec@...ts.infradead.org, linux-kernel@...r.kernel.org, hpa@...or.com, tglx@...utronix.de, mingo@...nel.org, kirill.shutemov@...ux.intel.com Subject: Re: [PATCH 3/3] x86/kdump/64: Change the upper limit of crashkernel reservation On 08/30/18 at 04:50pm, Kirill A. Shutemov wrote: > On Wed, Aug 29, 2018 at 10:16:24PM +0800, Baoquan He wrote: > > Restrict kdump to only reserve crashkernel below 64TB. Since the kdump > > jumping may be from 5-level to 4-level, and the kdump kernel is put > > above 64TB in 5-level kernel, then the jumping will fail. And the > > crashkernel reservation is done during the 1st kernel bootup, there's > > no way to detect the paging mode of kdump kernel at that time. > > > > Hence change the upper limmit of crashkernel reservation to 64TB > > s/limmit/limit/ Thanks, will change.
Powered by blists - more mailing lists