[amd64] Enable LEGACY_VSYSCALL_NONE instead of LEGACY_VSYSCALL_EMULATE

Closes: #852620

Nothing in the 'stretch' release uses vsyscall (so far as I can see),
so this is now safe to do.
This commit is contained in:
Ben Hutchings 2017-01-25 17:50:10 +00:00
parent 3479225d03
commit 74f87b226a
2 changed files with 6 additions and 2 deletions

4
debian/changelog vendored
View File

@ -4,6 +4,10 @@ linux (4.10~rc5-1~exp1) UNRELEASED; urgency=medium
[ Ben Hutchings ]
* [rt] Disable until it is updated for 4.10 or later
* [amd64] Enable LEGACY_VSYSCALL_NONE instead of LEGACY_VSYSCALL_EMULATE
(Closes: #852620). This breaks (e)glibc versions < 2.14 and dietlibc
versions < 0.33. It can be reverted using the kernel parameter:
vsyscall=emulate
-- Ben Hutchings <ben@decadent.org.uk> Tue, 24 Jan 2017 19:08:03 +0000

View File

@ -22,8 +22,8 @@ CONFIG_KEXEC_BZIMAGE_VERIFY_SIG=y
CONFIG_RANDOMIZE_MEMORY=y
## choice: vsyscall table for legacy applications
# CONFIG_LEGACY_VSYSCALL_NATIVE is not set
CONFIG_LEGACY_VSYSCALL_EMULATE=y
# CONFIG_LEGACY_VSYSCALL_NONE is not set
# CONFIG_LEGACY_VSYSCALL_EMULATE is not set
CONFIG_LEGACY_VSYSCALL_NONE=y
## end choice
CONFIG_PCI_MMCONFIG=y
CONFIG_ISA_DMA_API=y