lkml.org 
[lkml]   [2017]   [Apr]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Subject[PATCH 0/4] Handle memmap and mem kernel options in boot stage kaslr
Date
People reported kernel panic occurs during system boots up with mem boot option.
After checking code, several problems are found about memmap= and mem= in boot stage
kaslr.

*) In commit f28442497b5c ("x86/boot: Fix KASLR and memmap= collision"), only one memmap
entry is considered and only the last one if multiple memmap entries are specified.

*) mem= and memmap=nn[KMG] are not considered yet. They are used to limit max address
of system. Kernel can't be randomized to be above the limit.

*) kernel-parameters.txt doesn't tell the updated behaviour of memmap=.

This patchset tries to solve above issues.

Baoquan He (4):
param: Move function next_arg to lib/cmdline.c for later reuse
KASLR: Parse all memmap entries in cmdline
KASLR: Handle memory limit specified by memmap and mem option
doc: Update description about memmap option in kernel-parameter.txt

Documentation/admin-guide/kernel-parameters.txt | 9 ++
arch/x86/boot/compressed/cmdline.c | 2 +-
arch/x86/boot/compressed/kaslr.c | 161 ++++++++++++++----------
arch/x86/boot/string.c | 8 ++
include/linux/kernel.h | 1 +
kernel/params.c | 52 --------
lib/cmdline.c | 57 +++++++++
7 files changed, 172 insertions(+), 118 deletions(-)

--
2.5.5

\
 
 \ /
  Last update: 2017-04-17 15:35    [W:0.189 / U:1.532 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site