Bug was confirmed fixed per #5. Closing
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1326905
Title:
precise has wrong PTRACE_EV
This bug was fixed in the package linux - 3.2.0-65.98
---
linux (3.2.0-65.98) precise; urgency=low
[ Joseph Salisbury ]
* Release Tracking Bug
- LP: #1328620
[ Kamal Mostafa ]
* [Config] add debian/gbp.conf
[ Upstream Kernel Changes ]
* Revert "macvlan : fix check
This bug was fixed in the package linux - 3.2.0-65.98
---
linux (3.2.0-65.98) precise; urgency=low
[ Joseph Salisbury ]
* Release Tracking Bug
- LP: #1328620
[ Kamal Mostafa ]
* [Config] add debian/gbp.conf
[ Upstream Kernel Changes ]
* Revert "macvlan : fix check
I've confirmed this is fixed. Thanks!
$ cat /proc/version_signature
Ubuntu 3.2.0-65.98-generic 3.2.60
$ ./seccomp_bpf_tests
...
[ RUN ] TRACE.read_has_side_effects
[ OK ] TRACE.read_has_side_effects
[ RUN ] TRACE.getpid_runs_normally
[ OK ] TRACE.getpid_runs_normally
...
*
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
precise' to 'verification-done-precise'.
If verification is not done by 5 working days from
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1326905
Title:
precise has wrong PTRACE_EVENT_SECCOMP value
To manage notifications about this bug go to:
https://bugs.launchpad.n
Patch already sent to mailing list:
https://lists.ubuntu.com/archives/kernel-team/2014-June/043473.html
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu Precise)
Importance: Undecided => High
** Tags added: kernel-da-key kernel-stable-key
** Changed
** Description changed:
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 mana
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_SECCOMP7
** Patch added:
"
