From: Chao Fan <fanc.fnst@cn.fujitsu.com>
To: <tglx@linutronix.de>, <mingo@redhat.com>, <hpa@zytor.com>,
<x86@kernel.org>, <linux-kernel@vger.kernel.org>,
<keescook@chromium.org>, <bhe@redhat.com>, <rafael@kernel.org>
Cc: <indou.takao@jp.fujitsu.com>, <caoj.fnst@cn.fujitsu.com>,
<douly.fnst@cn.fujitsu.com>
Subject: Re: [PATCH v6 0/3] x86/boot/KASLR: Parse ACPI table and limit kaslr in immovable memory.
Date: Tue, 11 Sep 2018 09:13:31 +0800 [thread overview]
Message-ID: <20180911011331.GB8519@localhost.localdomain> (raw)
In-Reply-To: <20180910124015.18073-1-fanc.fnst@cn.fujitsu.com>
sorry, the cover letter forwand to rafael.
Thanks,
Chao Fan
On Mon, Sep 10, 2018 at 08:40:12PM +0800, Chao Fan wrote:
>***Background:
>People reported that kaslr may randomly chooses some positions
>which are located in movable memory regions. This will break memory
>hotplug feature and make the movable memory chosen by KASLR can't be
>removed.
>
>***Solutions:
>There should be a method to limit kaslr to choosing immovable memory
>regions, so there are 2 solutions:
>1) Add a kernel parameter to specify the memory regions.
>2) Get the information of memory hot-remove, then kaslr will know the
> right regions.
>In method 2, information about memory hot-remove is in ACPI
>tables, which will be parsed after start_kernel(), kaslr can't get
>the information.
>In method 1, users should know the regions address and specify in
>kernel parameter.
>
>In the earliest time, I tried to dig ACPI tabls to solve this problem.
>But I didn't splite the code in 'compressed/' and ACPI code, so the patch
>is hard to follow so refused by community.
>Somebody suggest to add a kernel parameter to specify the
>immovable memory so that limit kaslr in these regions. Then I make
>a new patchset. After several versions, Ingo gave a suggestion:
>https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1634024.html
>Follow Ingo's suggestion, imitate the ACPI code to parse the acpi
>tables, so that the kaslr can get necessary memory information in
>ACPI tables.
>I think ACPI code is an independent part, so copy the codes
>and functions to 'compressed/' directory, so that kaslr won't
>influence the initialization of ACPI.
>
>PATCH 1/3 Add acpitb.c to provide functions to parse ACPI code.
>PATCH 2/3 If CONFIG_MEMORY_HOTREMOVE enabled, walk all nodes and
> store the information of immovable memory regions.
>PATCH 3/3 According to the immovable memory regions, filter the
> immovable regions which KASLR can choose.
>
>***Test results:
> - I did a very simple test, and it can get the memory information in
> bios and efi KVM guest machine, and put it by early printk. But no
> more tests, so it's with RFC tag.
>
>v1->v2:
> - Simplify some code.
>Follow Baoquan He's suggestion:
> - Reuse the head file of acpi code.
>
>v2->v3:
> - Test in more conditions, so remove the 'RFC' tag.
> - Change some comments.
>
>v3->v4:
>Follow Thomas Gleixner's suggetsion:
> - Put the whole efi related function into #define CONFIG_EFI and return
> false in the other stub.
> - Simplify two functions in head file.
>
>v4->v5:
>Follow Dou Liyang's suggestion:
> - Add more comments about some functions based on kernel code.
> - Change some typo in comments.
> - Clean useless variable.
> - Add check for the boundary of array.
> - Add check for 'movable_node' parameter
>
>v5->v6:
>Follow Baoquan He's suggestion:
> - Change some log.
> - Add the check for acpi_rsdp
> - Change some code logical to make code clear
>
>Any comments will be welcome.
>
>
>Chao Fan (3):
> x86/boot: Add acpitb.c to parse acpi tables
> x86/boot/KASLR: Walk srat tables to filter immovable memory
> x86/boot/KASLR: Limit kaslr to choosing the immovable memory
>
> arch/x86/boot/compressed/Makefile | 4 +
> arch/x86/boot/compressed/acpitb.c | 382 ++++++++++++++++++++++++++++++
> arch/x86/boot/compressed/kaslr.c | 76 +++++-
> arch/x86/boot/compressed/misc.h | 8 +
> 4 files changed, 459 insertions(+), 11 deletions(-)
> create mode 100644 arch/x86/boot/compressed/acpitb.c
>
>--
>2.17.1
>
next prev parent reply other threads:[~2018-09-11 1:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 12:40 [PATCH v6 0/3] x86/boot/KASLR: Parse ACPI table and limit kaslr in immovable memory Chao Fan
2018-09-10 12:40 ` [PATCH v6 1/3] x86/boot: Add acpitb.c to parse acpi tables Chao Fan
2018-09-10 20:13 ` Rafael J. Wysocki
2018-09-11 1:27 ` Chao Fan
2018-09-11 7:41 ` Rafael J. Wysocki
2018-09-11 7:52 ` Chao Fan
2018-09-11 8:52 ` kbuild test robot
2018-09-11 8:52 ` [RFC PATCH] x86/boot: get_acpi_srat_table() can be static kbuild test robot
2018-09-11 8:55 ` Chao Fan
2018-09-12 7:08 ` [PATCH v6 1/3] x86/boot: Add acpitb.c to parse acpi tables kbuild test robot
2018-09-10 12:40 ` [PATCH v6 2/3] x86/boot/KASLR: Walk srat tables to filter immovable memory Chao Fan
2018-09-10 12:40 ` [PATCH v6 3/3] x86/boot/KASLR: Limit kaslr to choosing the " Chao Fan
2018-09-11 1:13 ` Chao Fan [this message]
2018-09-11 7:28 ` [PATCH v6 0/3] x86/boot/KASLR: Parse ACPI table and limit kaslr in " Rafael J. Wysocki
2018-09-11 7:53 ` Chao Fan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180911011331.GB8519@localhost.localdomain \
--to=fanc.fnst@cn.fujitsu.com \
--cc=bhe@redhat.com \
--cc=caoj.fnst@cn.fujitsu.com \
--cc=douly.fnst@cn.fujitsu.com \
--cc=hpa@zytor.com \
--cc=indou.takao@jp.fujitsu.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rafael@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox