lkml.org 
[lkml]   [2011]   [Jun]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
From
Subject[PATCH v5 9/9] x86-64: Add CONFIG_UNSAFE_VSYSCALLS to feature-removal-schedule
Date
CONFIG_UNSAFE_VSYSCALLS was added in the previous patch as a
temporary hack to avoid penalizing users who don't build glibc from
git.

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 1a9446b..94b4470 100644
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -600,3 +600,12 @@ Why: Superseded by the UVCIOC_CTRL_QUERY ioctl.
Who: Laurent Pinchart <laurent.pinchart@ideasonboard.com>

----------------------------
+
+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.2


\
 
 \ /
  Last update: 2011-06-05 20:05    [W:0.135 / U:1.188 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site