Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1458392
| From | "H. Peter Anvin" <hpa@zytor.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v1 2/2] x86/KASLR: Increase BRK pages for KASLR memory randomization |
| Date | 2016-08-09 06:20 +0200 |
| Message-ID | <s46Gd-2wQ-1@gated-at.bofh.it> (permalink) |
| References | <s3XMC-52s-9@gated-at.bofh.it> <s3XMC-52s-17@gated-at.bofh.it> <s46wx-2tH-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On August 8, 2016 9:01:42 PM PDT, Borislav Petkov <bp@suse.de> wrote: >On Mon, Aug 08, 2016 at 11:40:07AM -0700, Thomas Garnier wrote: >> Default implementation expects 6 pages maximum are needed for low >page >> allocations. If KASLR memory randomization is enabled, the worse case >> of e820 layout would require 12 pages (no large pages). It is due to >the >> PUD level randomization and the variable e820 memory layout. > >Can't this number of required pages be computed based on the >randomization offset or somesuch instead of maxing it out by default on >every machine which enables CONFIG_RANDOMIZE_MEMORY? > >> This bug was found while doing extensive testing of KASLR memory >> randomization on different type of hardware. >> >> Signed-off-by: Thomas Garnier <thgarnie@google.com> >> --- >> Based on next-20160805 >> --- >> arch/x86/mm/init.c | 8 ++++++++ >> 1 file changed, 8 insertions(+) >> >> diff --git a/arch/x86/mm/init.c b/arch/x86/mm/init.c >> index 6209289..3a27e6a 100644 >> --- a/arch/x86/mm/init.c >> +++ b/arch/x86/mm/init.c >> @@ -130,6 +130,14 @@ void __init early_alloc_pgt_buf(void) >> unsigned long tables = INIT_PGT_BUF_SIZE; >> phys_addr_t base; >> >> + /* >> + * Depending on the machine e860 memory layout and the PUD >alignement. > > e820 alignment > >> + * We may need twice more pages when KASLR memoy randomization is > > memory > >> + * enabled. >> + */ >> + if (IS_ENABLED(CONFIG_RANDOMIZE_MEMORY)) >> + tables *= 2; >> + >> base = __pa(extend_brk(tables, PAGE_SIZE)); >> >> pgt_buf_start = base >> PAGE_SHIFT; >> -- >> 2.8.0.rc3.226.g39d4020 >> Upping the brk by a few pages is not a big deal. Unused brk gets reclaimed at init release time. -- Sent from my Android device with K-9 Mail. Please excuse brevity and formatting.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH v1 1/2] x86/KASLR: Fix physical memory calculation on KASLR memory randomization Thomas Garnier <thgarnie@google.com> - 2016-08-08 20:50 +0200
[PATCH v1 2/2] x86/KASLR: Increase BRK pages for KASLR memory randomization Thomas Garnier <thgarnie@google.com> - 2016-08-08 20:50 +0200
Re: [PATCH v1 2/2] x86/KASLR: Increase BRK pages for KASLR memory randomization Borislav Petkov <bp@suse.de> - 2016-08-09 06:10 +0200
Re: [PATCH v1 2/2] x86/KASLR: Increase BRK pages for KASLR memory randomization "H. Peter Anvin" <hpa@zytor.com> - 2016-08-09 06:20 +0200
Re: [PATCH v1 2/2] x86/KASLR: Increase BRK pages for KASLR memory randomization Thomas Garnier <thgarnie@google.com> - 2016-08-09 17:00 +0200
Re: [PATCH v1 1/2] x86/KASLR: Fix physical memory calculation on KASLR memory randomization Joerg Roedel <jroedel@suse.de> - 2016-08-09 18:10 +0200
Re: [PATCH v1 1/2] x86/KASLR: Fix physical memory calculation on KASLR memory randomization Thomas Garnier <thgarnie@google.com> - 2016-08-09 18:40 +0200
Re: [PATCH v1 1/2] x86/KASLR: Fix physical memory calculation on KASLR memory randomization Thomas Garnier <thgarnie@google.com> - 2016-08-09 18:10 +0200
csiph-web