linux-kernel - [PATCH 0/2] Fix and re-enable vsyscall=emulate

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon,  7 Nov 2011 16:33:39 -0800
From:	Andy Lutomirski <luto@...capital.net>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	x86@...nel.org, Ingo Molnar <mingo@...e.hu>,
	richard -rw- weinberger <richard.weinberger@...il.com>,
	Adrian Bunk <bunk@...sta.de>,
	"H. Peter Anvin" <hpa@...ux.intel.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
	Andy Lutomirski <luto@...capital.net>
Subject: [PATCH 0/2] Fix and re-enable vsyscall=emulate

The really nice fix (wiring up access_ok failures to be able to raise
signals) won't be ready on time for 3.2, so let's try the simpler fix
for now.

Changes from the earlier version:
 - Clean up the odd ptr==0 check.
 - Flip the default back to vsyscall=emulate

Andy Lutomirski (2):
  x86-64: Set siginfo and context on vsyscall emulation faults
  x86: Default to vsyscall=emulate

 Documentation/kernel-parameters.txt |    7 +--
 arch/x86/include/asm/thread_info.h  |    3 +-
 arch/x86/include/asm/uaccess.h      |    2 +-
 arch/x86/kernel/vsyscall_64.c       |   77 ++++++++++++++++++++++++++++++----
 arch/x86/mm/extable.c               |    2 +-
 arch/x86/mm/fault.c                 |   22 +++++++---
 6 files changed, 91 insertions(+), 22 deletions(-)

-- 
1.7.6.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/