On Mon, 2017-01-02 at 09:29 +0100, Harald Dunkel wrote: > Hi folks, > > Running 4.8.11 from the backports repository for Jessie I found > this in kern.log: > > Jan 1 03:00:53 dpcl082 kernel: [829504.082278] dpkg[24427] vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7fff8cb7c818 ax:ffffffffff600400 si:428720 di:7fff8cb7c830 > Jan 1 03:00:53 dpcl082 kernel: [829504.082281] dpkg[24427]: segfault at ffffffffff600400 ip ffffffffff600400 sp 00007fff8cb7c818 error 15 > > AFAICT this happened during the unattended upgrades at night. > I haven't seen this error in interactive use yet. But its > dpkg 1.17.27, not some weird binary-only package grabbed from > a 3rd-party repository. It's probably dpkg in a wheezy (or earlier) chroot. > I wonder if setting vsyscall=none in the backports kernel is > a good idea. Is it safe to use together with Jessie's regular > packages? This is safe with anything using glibc, but not with those packages using dietlibc. Because of that, I reverted this change 4.8.15-1 (but I will make the change again after the stretch release). In the mean time, you can use the command line parameter vsyscall=emulate. Ben. -- Ben Hutchings Q. Which is the greater problem in the world today, ignorance or apathy? A. I don't know and I couldn't care less.
Attachment:
signature.asc
Description: This is a digitally signed message part