kernel-packages team mailing list archive

[Joseph Salisbury <joseph.salisbury@xxxxxxxxxxxxx>]

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 in: linux (Ubuntu)
       Status: Incomplete => Triaged

** Changed in: linux (Ubuntu Precise)
       Status: Incomplete => Triaged

-- 
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:
  Triaged
Status in “linux” source package in Precise:
  Triaged

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.

  SRU Justification:
  Impact: seccomp filters using ptrace managers don't work on precise
  Fix: fix ptrace flag numbering to match all other released kernel versions
  Testcase: https://github.com/kees/seccomp/tree/ptrace

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1326905/+subscriptions