From 96bd7ea325d62018981fcae5f728456adcb9e8f5 Mon Sep 17 00:00:00 2001 From: maximilian attems Date: Wed, 16 Apr 2008 19:36:36 +0200 Subject: [PATCH] --- yaml --- r: 88454 b: refs/heads/master c: 5f46ce14bd432cf52bf91079270af164ca48f821 h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/security/Kconfig | 10 ++++++---- 2 files changed, 7 insertions(+), 5 deletions(-) diff --git a/[refs] b/[refs] index aef449f07c68..26398561ba94 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 27cc2a6e572e1a86a08a02918517558f175f6974 +refs/heads/master: 5f46ce14bd432cf52bf91079270af164ca48f821 diff --git a/trunk/security/Kconfig b/trunk/security/Kconfig index 5dfc206748cf..49b51f964897 100644 --- a/trunk/security/Kconfig +++ b/trunk/security/Kconfig @@ -113,10 +113,12 @@ 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 - functionality would either need additional permissions from either - the LSM or the capabilities module or have this protection disabled. + For most ia64, ppc64 and 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. This value can be changed after boot using the /proc/sys/vm/mmap_min_addr tunable.