From: Andy Lutomirski <luto@MIT.EDU>
To: Ingo Molnar <mingo@elte.hu>, x86@kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, Jesper Juhl <jj@chaosbits.net>,
Borislav Petkov <bp@alien8.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Arjan van de Ven <arjan@infradead.org>,
Jan Beulich <JBeulich@novell.com>,
richard -rw- weinberger <richard.weinberger@gmail.com>,
Mikael Pettersson <mikpe@it.uu.se>,
Andi Kleen <andi@firstfloor.org>, Andy Lutomirski <luto@MIT.EDU>
Subject: [PATCH v3 10/10] x86-64: Add CONFIG_UNSAFE_VSYSCALLS to feature-removal-schedule
Date: Tue, 31 May 2011 09:16:04 -0400 [thread overview]
Message-ID: <7e604b2dd699a30204fda3d1011f3af5a2c56572.1306847455.git.luto@mit.edu> (raw)
In-Reply-To: <cover.1306847455.git.luto@mit.edu>
In-Reply-To: <cover.1306847455.git.luto@mit.edu>
Signed-off-by: Andy Lutomirski <luto@mit.edu>
---
Documentation/feature-removal-schedule.txt | 9 +++++++++
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index 492e81d..db7a122 100644
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -580,3 +580,12 @@ Why: These legacy callbacks should no longer be used as i2c-core offers
Who: Jean Delvare <khali@linux-fr.org>
----------------------------
+
+What: CONFIG_UNSAFE_VSYSCALLS (x86_64)
+When: When glibc 2.14 or newer is ubitquitous. Perhaps mid-2012.
+Why: Having user-executable code at a fixed address is a security problem.
+ Turning off CONFIG_UNSAFE_VSYSCALLS mostly removes the risk but will
+ make the time() function slower on glibc versions 2.13 and below.
+Who: Andy Lutomirski <luto@mit.edu>
+
+----------------------------
--
1.7.5.1
next prev parent reply other threads:[~2011-05-31 13:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 13:15 [PATCH v3 00/10] Remove syscall instructions at fixed addresses Andy Lutomirski
2011-05-31 13:15 ` [PATCH v3 01/10] x86-64: Fix alignment of jiffies variable Andy Lutomirski
2011-05-31 13:15 ` [PATCH v3 02/10] x86-64: Document some of entry_64.S Andy Lutomirski
2011-05-31 13:15 ` [PATCH v3 03/10] x86-64: Give vvars their own page Andy Lutomirski
2011-05-31 13:15 ` [PATCH v3 04/10] x86-64: Remove kernel.vsyscall64 sysctl Andy Lutomirski
2011-05-31 13:15 ` [PATCH v3 05/10] x86-64: Map the HPET NX Andy Lutomirski
2011-05-31 13:16 ` [PATCH v3 06/10] x86-64: Remove vsyscall number 3 (venosys) Andy Lutomirski
2011-05-31 13:16 ` [PATCH v3 07/10] x86-64: Fill unused parts of the vsyscall page with 0xcc Andy Lutomirski
2011-05-31 13:16 ` [PATCH v3 08/10] x86-64: Emulate legacy vsyscalls Andy Lutomirski
2011-06-01 11:54 ` Brian Gerst
2011-06-01 12:36 ` Andrew Lutomirski
2011-05-31 13:16 ` [PATCH v3 09/10] x86-64: Randomize int 0xcc magic al values at boot Andy Lutomirski
2011-05-31 13:16 ` Andy Lutomirski [this message]
2011-06-01 17:35 ` [PATCH v3 10/10] x86-64: Add CONFIG_UNSAFE_VSYSCALLS to feature-removal-schedule Valdis.Kletnieks
2011-06-01 17:41 ` Andrew Lutomirski
2011-06-01 18:27 ` Valdis.Kletnieks
2011-06-02 8:09 ` Ingo Molnar
2011-05-31 13:45 ` [PATCH v3 00/10] Remove syscall instructions at fixed addresses Ingo Molnar
2011-05-31 13:54 ` Andrew Lutomirski
2011-05-31 14:13 [PATCH v4 " Andy Lutomirski
2011-05-31 14:14 ` [PATCH v4 10/10] x86-64: Add CONFIG_UNSAFE_VSYSCALLS to feature-removal-schedule Andy Lutomirski
2011-05-31 18:34 ` Andi Kleen
2011-05-31 18:59 ` Andrew Lutomirski
2011-05-31 19:28 ` Ingo Molnar
2011-05-31 19:36 ` Ingo Molnar
2011-08-06 20:18 ` [PATCH v3 " Andrew Lutomirski
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=7e604b2dd699a30204fda3d1011f3af5a2c56572.1306847455.git.luto@mit.edu \
--to=luto@mit.edu \
--cc=JBeulich@novell.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=arjan@infradead.org \
--cc=bp@alien8.de \
--cc=jj@chaosbits.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
--cc=mingo@elte.hu \
--cc=richard.weinberger@gmail.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/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®