Messages in this thread Patch in this message | | | From | Andy Lutomirski <> | Subject | [PATCH v4 10/10] x86-64: Add CONFIG_UNSAFE_VSYSCALLS to feature-removal-schedule | Date | Tue, 31 May 2011 10:14:08 -0400 |
| |
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.1
| |