Wrong: $ cd /src/kernels/ubuntu/precise ; git grep PTRACE_EVENT_SECCOMP ... include/linux/ptrace.h:#define PTRACE_EVENT_SECCOMP 8
Correct: $ cd /src/kernels/ubuntu/trusty ; git grep PTRACE_EVENT_SECCOMP ... include/uapi/linux/ptrace.h:#define PTRACE_EVENT_SECCOMP 7 ** Patch added: "0001-ptrace-renumber-PTRACE_EVENT_STOP-so-that-future-new.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1326905/+attachment/4125988/+files/0001-ptrace-renumber-PTRACE_EVENT_STOP-so-that-future-new.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1326905 Title: precise has wrong PTRACE_EVENT_SECCOMP value Status in “linux” package in Ubuntu: Incomplete Status in “linux” source package in Precise: Incomplete Bug description: In v3.2, there was confusion over the new "PTRACE_EVENT_EXIT" value. Ultimately, upstream fixed it, but in the precise backporting of seccomp, the wrong value was used: 5cdf389aee90109e2e3d88085dea4dd5508a3be7 As a result, seccomp filteres expecting ptrace managers don't work correctly on precise. The attached patch backports the upstream PTRACE_EVENT_EXIT value and restores the correct PTRACE_EVENT_SECCOMP value. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1326905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
