LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com> To: linux-kernel@vger.kernel.org, mingo@kernel.org, lcapitulino@redhat.com, keescook@chromium.org, tglx@linutronix.de Cc: x86@kernel.org, hpa@zytor.com, fanc.fnst@cn.fujitsu.com, yasu.isimatu@gmail.com, indou.takao@jp.fujitsu.com, douly.fnst@cn.fujitsu.com, Baoquan He <bhe@redhat.com> Subject: [PATCH 0/2] x86/boot/KASLR: Skip specified number of 1GB huge pages when do physical randomization Date: Wed, 16 May 2018 18:05:30 +0800 [thread overview] Message-ID: <20180516100532.14083-1-bhe@redhat.com> (raw) This is a regression bug fix. Luiz's team reported that 1GB huge page allocation will get one less 1GB page randomly when KASLR is enabled. On their KVM guest with 4GB RAM, which only has one good 1GB huge page, they found the 1GB huge page allocation sometime failed with below kernel option adding. default_hugepagesz=1G hugepagesz=1G hugepages=1 This is because kernel may be randomized into those good 1GB huge pages. I ever thought to solve this by specifying available memory regions which kernel KASLR can be randomized into to avoid those good 1GB huge pages. Chao's patches can be used to fix it: https://lkml.org/lkml/2018/2/28/217 Later, Ingo suggested avoiding them in boot KASLR code. https://lkml.org/lkml/2018/3/12/312 So I made this patchset to handle the conflict between 1GB huge pages allocation and KASLR. Any idea or suggestion about the handling, function naming is appreciated. Baoquan He (2): x86/boot/KASLR: Add two functions for 1GB huge pages handling x86/boot/KASLR: Skip specified number of 1GB huge pages when do physical randomization arch/x86/boot/compressed/kaslr.c | 84 +++++++++++++++++++++++++++++++++++++--- 1 file changed, 79 insertions(+), 5 deletions(-) -- 2.13.6
next reply other threads:[~2018-05-16 10:08 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-05-16 10:05 Baoquan He [this message] 2018-05-16 10:05 ` [PATCH 1/2] x86/boot/KASLR: Add two functions for 1GB huge pages handling Baoquan He 2018-05-17 3:27 ` Chao Fan 2018-05-17 4:03 ` Baoquan He 2018-05-17 5:53 ` Chao Fan 2018-05-17 6:13 ` Baoquan He 2018-05-17 5:12 ` damian 2018-05-17 5:38 ` Baoquan He 2018-06-21 15:01 ` Ingo Molnar 2018-06-22 12:14 ` Baoquan He 2018-06-24 7:13 ` Ingo Molnar 2018-05-16 10:05 ` [PATCH 2/2] x86/boot/KASLR: Skip specified number of 1GB huge pages when do physical randomization Baoquan He 2018-05-18 7:00 ` [PATCH 0/2] " Ingo Molnar 2018-05-18 7:43 ` Baoquan He 2018-05-18 8:19 ` Ingo Molnar 2018-05-18 11:28 ` Baoquan He 2018-05-18 12:14 ` Baoquan He 2018-05-23 19:10 ` Luiz Capitulino 2018-05-28 9:54 ` Baoquan He 2018-05-29 13:27 ` Luiz Capitulino
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=20180516100532.14083-1-bhe@redhat.com \ --to=bhe@redhat.com \ --cc=douly.fnst@cn.fujitsu.com \ --cc=fanc.fnst@cn.fujitsu.com \ --cc=hpa@zytor.com \ --cc=indou.takao@jp.fujitsu.com \ --cc=keescook@chromium.org \ --cc=lcapitulino@redhat.com \ --cc=linux-kernel@vger.kernel.org \ --cc=mingo@kernel.org \ --cc=tglx@linutronix.de \ --cc=x86@kernel.org \ --cc=yasu.isimatu@gmail.com \ /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: linkBe 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; as well as URLs for NNTP newsgroup(s).