[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181013220541.GI31650@zn.tnic>
Date: Sun, 14 Oct 2018 00:05:41 +0200
From: Borislav Petkov <bp@...en8.de>
To: Masayoshi Mizuma <msys.mizuma@...il.com>
Cc: Chao Fan <fanc.fnst@...fujitsu.com>, Baoquan He <bhe@...hat.com>,
Ingo Molnar <mingo@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
linux-kernel@...r.kernel.org, x86@...nel.org,
linux-efi@...r.kernel.org, linux-acpi@...r.kernel.org,
mingo@...hat.com, hpa@...or.com, keescook@...omium.org,
rjw@...ysocki.net, lenb@...nel.org, ard.biesheuvel@...aro.org,
indou.takao@...fujitsu.com, caoj.fnst@...fujitsu.com
Subject: Re: [PATCH v8 0/3] x86/boot/KASLR: Parse ACPI table and limit kaslr
in immovable memory
On Sat, Oct 13, 2018 at 05:45:51PM -0400, Masayoshi Mizuma wrote:
> Yes, but I think we need to arrange the Chao's SRAT parsing to be used
> from kernel_randomize_memory() because Chao's approach needs the SRAT
> parsing before extract kernel and the padding size calculation needs
> the parsing in start_kernel(), so they are living in different life
> cycle and space.
Or you would like to pass some info from the compressed kernel to kernel
proper?
For example, something like the passing in add_e820ext() and the consumtion
in parse_setup_data():
switch (data_type) {
case SETUP_E820_EXT:
e820__memory_setup_extended(pa_data, data_len);
So info you need for your padding gets collected in
arch/x86/boot/compressed/acpitb.c and you consume it in
kernel_randomize_memory()?
Would that work?
:-)
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
Powered by blists - more mailing lists