lkml.org 
[lkml]   [2008]   [Apr]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
From
Subject[PATCH] Kconfig: enhance DEFAULT_MMAP_MIN_ADDR description
Date
Got burned by setting the proposed default of 65536
across all Debian archs.

Thus proposing to be more specific on which archs you may
set this. Also propose a value for arm and friends that
doesn't break sshd.

Signed-off-by: maximilian attems <max@stro.at>
Cc: Martin Michlmayr <tbm@cyrius.com>
Cc: Gordon Farquharson <gordonfarquharson@gmail.com>
---
security/Kconfig | 5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/security/Kconfig b/security/Kconfig
index 5dfc206..cc1e4bd 100644
--- a/security/Kconfig
+++ b/security/Kconfig
@@ -113,8 +113,9 @@ config SECURITY_DEFAULT_MMAP_MIN_ADDR
from userspace allocation. Keeping a user from writing to low pages
can help reduce the impact of kernel NULL pointer bugs.

- For most users with lots of address space a value of 65536 is
- reasonable and should cause no problems. Programs which use vm86
+ For most x86 users with lots of address space a value of 65536 is
+ reasonable and should cause no problems. On arm and other archs
+ it should not be higher than 32768. Programs which use vm86
functionality would either need additional permissions from either
the LSM or the capabilities module or have this protection disabled.

--
1.5.5


\
 
 \ /
  Last update: 2008-04-16 19:17    [W:0.107 / U:0.468 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site