[FEAT] Upgrade libseccomp from 2.2.3 ->2.3.1

Bug #1580558 reported by bugproxy
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ubuntu on IBM z Systems
Fix Released
Medium
Dimitri John Ledkov
libseccomp (Ubuntu)
Fix Released
Medium
Skipper Bug Screeners

Bug Description

== Comment: #1 - Heinz-Werner Seeck <email address hidden> - 2016-05-11 05:09:09 ==
Please upgrade package libseccomp.
The new version 2.3.1 is available on github

https://github.com/seccomp/libseccomp/releases

== Comment: #2 - Heinz-Werner Seeck <email address hidden> - 2016-05-11 05:10:59 ==
?Version 2.3.0 - February 29, 2016
?Added support for the s390 and s390x architectures
?Added support for the ppc, ppc64, and ppc64le architectures
?Update the internal syscall tables to match the Linux 4.5-rcX releases
?Filter generation for both multiplexed and direct socket syscalls on x86
?Support for the musl libc implementation
?Additions to the API to enable runtime version checking of the library
?Enable the use of seccomp() instead of prctl() on supported systems
?Added additional tests to the regression test suite

?Version 2.3.1 - April 20, 2016
?Fixed a problem with 32-bit x86 socket syscalls on some systems
?Fixed problems with ipc syscalls on 32-bit x86
?Fixed problems with socket and ipc syscalls on s390 and s390x

bugproxy (bugproxy)
tags: added: architecture-s39064 bugnameltc-141261 severity-high targetmilestone-inin1610
Changed in ubuntu:
assignee: nobody → Skipper Bug Screeners (skipper-screen-team)
affects: ubuntu → libseccomp (Ubuntu)
Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
importance: Undecided → Medium
Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
assignee: nobody → Dimitri John Ledkov (xnox)
status: New → Triaged
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in libseccomp (Ubuntu):
status: New → Confirmed
Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
status: Triaged → Confirmed
Revision history for this message
Ricardo (ricardo-smartmatic) wrote :

This package should be moved from backports to updates to allow Docker support for seccomp:

https://github.com/docker/docker/issues/22870#

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

@ricardo-smartmatic

This bug is about upgrading libseccomp in 16.10 without considering implications of docker integration on 16.10, 16.04 and/or 14.04. Could you open a new request something along the lines "Please support seccomp with docker" affecting libseccomp and docker packages?

Jeremy Bícha (jbicha)
tags: added: upgrade-software-version
Changed in libseccomp (Ubuntu):
status: Confirmed → In Progress
importance: Undecided → Medium
Changed in libseccomp (Ubuntu):
status: In Progress → Fix Committed
Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
status: Confirmed → Fix Committed
tags: added: block-proposed
tags: removed: block-proposed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libseccomp - 2.3.1-2ubuntu2

---------------
libseccomp (2.3.1-2ubuntu2) yakkety; urgency=medium

  * Fix autopkgtest, seccomp resolution now returns negative syscall
    numbers for multiplexed calls, thus direct access symbols roundtrip is
    via negative numbers. E.g. 373 -> shutdown -> -113 -> shutdown.

libseccomp (2.3.1-2ubuntu1) yakkety; urgency=medium

  * Merge with Debian unstable LP: #1580558. Remaining Ubuntu changes:
    - Add autopkgtests. (Closes: #788577)

 -- Dimitri John Ledkov <email address hidden> Fri, 10 Jun 2016 18:14:04 +0100

Changed in libseccomp (Ubuntu):
status: Fix Committed → Fix Released
Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
status: Fix Committed → Fix Released
summary: - Upgrade libseccomp from 2.2.3 ->2.3.1
+ [FEAT] Upgrade libseccomp from 2.2.3 ->2.3.1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.