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.
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: 5cdf389aee90109 e2e3d88085dea4d d5508a3be7
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.