[amd64] Re-enable LEGACY_VSYSCALL_EMULATE instead of LEGACY_VSYSCALL_NONE

There are still binaries in stable that use vsyscall (via dietlibc).
Since dietlibc is statically linked and some of the packages are also
backported from unstable, we can't use versioned Breaks to force
upgrades.
This commit is contained in:
Ben Hutchings 2016-12-09 13:27:04 +00:00
parent 3a2602da33
commit 33f253b15d
2 changed files with 6 additions and 2 deletions

4
debian/changelog vendored
View File

@ -49,6 +49,10 @@ linux (4.8.12-1) UNRELEASED; urgency=medium
* net: avoid signed overflows for SO_{SND|RCV}BUFFORCE (CVE-2016-9793)
* Add ABI reference for 4.8.0-2
[ Ben Hutchings ]
* [amd64] Re-enable LEGACY_VSYSCALL_EMULATE instead of LEGACY_VSYSCALL_NONE.
There are still binaries in stable that use vsyscall (via dietlibc).
-- Uwe Kleine-König <ukleinek@debian.org> Sun, 04 Dec 2016 21:16:06 +0100
linux (4.8.11-1) unstable; urgency=medium

View File

@ -20,8 +20,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 is not set
CONFIG_LEGACY_VSYSCALL_NONE=y
CONFIG_LEGACY_VSYSCALL_EMULATE=y
# CONFIG_LEGACY_VSYSCALL_NONE is not set
## end choice
CONFIG_PCI_MMCONFIG=y
CONFIG_ISA_DMA_API=y