From: maximilian attems <max@stro.at>
To: Eric Paris <eparis@redhat.com>
Cc: James Morris <jmorris@namei.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Russell King <rmk+kernel@arm.linux.org.uk>,
maximilian attems <max@stro.at>,
Martin Michlmayr <tbm@cyrius.com>,
Gordon Farquharson <gordonfarquharson@gmail.com>
Subject: [PATCH] Kconfig: enhance DEFAULT_MMAP_MIN_ADDR description
Date: Wed, 16 Apr 2008 19:13:44 +0200 [thread overview]
Message-ID: <1208366024-20261-1-git-send-email-max@stro.at> (raw)
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
next reply other threads:[~2008-04-16 17:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-16 17:13 maximilian attems [this message]
2008-04-16 17:23 ` Eric Paris
2008-04-16 17:36 ` maximilian attems
2008-04-16 23:42 ` James Morris
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=1208366024-20261-1-git-send-email-max@stro.at \
--to=max@stro.at \
--cc=akpm@linux-foundation.org \
--cc=eparis@redhat.com \
--cc=gordonfarquharson@gmail.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=tbm@cyrius.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: link
Be 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
all inboxes | Powered by JetHome®