This bug was fixed in the package libseccomp - 2.1.1-1ubuntu1~trusty3
---
libseccomp (2.1.1-1ubuntu1~trusty3) trusty-proposed; urgency=medium
* Cherrypick various bpf fixes to support argument filtering on 64-bit
(LP: #1653487)
- debian/patches/bpf-use-state-arch.patch: use
There are a lot of failures and containers don't seem to be starting for
a variety of reasons. lxc 1.0.8 (what this version of libseccomp was
tested against) always failed on armhf according to
http://autopkgtest.ubuntu.com/packages/l/lxc/trusty/armhf. 1.0.7 also
always failed. 1.0.9 started to pas
http://autopkgtest.ubuntu.com/packages/l/lxc/trusty/armhf
** Tags removed: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1450642
Title:
seccomp missing many new syscalls
To manag
There's an autopkgtest lxc failure on armhf, which usually passes.
Please could you determine if this is caused by this SRU? Removing
verification-done for now to avoid any accidents. Please set back if you
determine that the autopkgtest failure has a cause unrelated to this
SRU.
--
You received
I've completed my verification of 2.1.1-1ubuntu1~trusty3 SRU for amd64
and i386.
I followed the test plan for this and bug #1653487 with additional
manual testing for lxc and docker debs along with various snaps (ufw,
lxd, docker (amd64 only since docker upstream doesn't provide 32 bit
images; als
@Tyler, the problem in bug #1653487 was due to a latent bug in
libseccomp 2.1 that is only exposed via snap-confine's use of argument
filtering. I'm uploading 2.1.1-1ubuntu1~trusty3 now and will do the
verification.
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
** Description changed:
[Impact]
Several syscalls were discovered to be missing when using the launcher on
snappy. These should be added so we may properly support seccomp filtering.
[Test Case]
seccomp itself has a comprehensive testsuite, and while it doesn't fail the
build, regress
I'm setting the tag back to verification-needed then to prevent this
from being released.
** Tags removed: verification-done
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
I wanted to mention that snaps were working with libseccomp from trusty-
proposed in my testing. I tested with the hello-world, pwgen-tyhicks,
and lxd snaps on amd64. However, bug #1653487 shows there is a snapd
build test failure with the libseccomp from trusty-proposed and it needs
to be triaged
Note bug #1653487 which says that this SRU is not enough to get seccomp
working with snaps on 64 bit systems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1450642
Title:
seccomp missing many new sy
I've completed my verification of the libseccomp 2.1.1-1ubuntu1~trusty1
SRU.
I followed the test plan and everything went as expected. I think this
SRU is good to go.
** Tags removed: verification-needed
** Tags added: verification-complete
** Tags removed: verification-complete
** Tags added: v
** Description changed:
[Impact]
Several syscalls were discovered to be missing when using the launcher on
snappy. These should be added so we may properly support seccomp filtering.
[Test Case]
seccomp itself has a comprehensive testsuite, and while it doesn't fail the
build, regress
** Changed in: libseccomp (Ubuntu)
Importance: Undecided => High
** Changed in: libseccomp (Ubuntu Vivid)
Importance: Undecided => High
** Changed in: libseccomp (Ubuntu Wily)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
Hello Jamie, or anyone else affected,
Accepted libseccomp into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libseccomp/2.1.1-1ubuntu1~trusty1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
** Description changed:
[Impact]
Several syscalls were discovered to be missing when using the launcher on
snappy. These should be added so we may properly support seccomp filtering.
[Test Case]
seccomp itself has a comprehensive testsuite, and while it doesn't fail the
build, regress
** Also affects: libseccomp (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: libseccomp (Ubuntu Trusty)
Status: New => In Progress
** Changed in: libseccomp (Ubuntu Trusty)
Importance: Undecided => High
** Changed in: libseccomp (Ubuntu Trusty)
Assignee:
** Changed in: snappy/15.04
Status: Fix Committed => 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/1450642
Title:
seccomp missing many new syscalls
To manage notifications about
** Also affects: snappy/15.04
Importance: Undecided
Status: New
** Changed in: snappy/15.04
Milestone: None => 15.04.1
** Changed in: snappy/15.04
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
** Changed in: snappy/15.04
Status: New => Fix Committed
** Changed
** Branch linked: lp:ubuntu/libseccomp
** Branch linked: lp:~ubuntu-branches/ubuntu/vivid/libseccomp/vivid-
proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1450642
Title:
seccomp missing man
This bug was fixed in the package libseccomp - 2.1.1-1ubuntu1~vivid2
---
libseccomp (2.1.1-1ubuntu1~vivid2) vivid-proposed; urgency=medium
* add-finit-module.patch: add finit_module syscalls to x86 and x86-64
syscall tables
* update syscalls for modern kernels (skipping MIPS)
** Project changed: snappy-ubuntu => snappy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1450642
Title:
seccomp missing many new syscalls
To manage notifications about this bug go to:
https://bugs
Test cases pass with packages in vivid-proposed:
* in build testsuite results are same between previous build and this for all
archs: PASS
* scmp_sys_resolver 1024: PASS
* scmp_sys_resolver getrandom: PASS
* autopkgtests: PASS
* lxc (amd64 and i386 only): PASS
* docker framework (snappy/armh
Hello Jamie, or anyone else affected,
Accepted libseccomp into vivid-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/libseccomp/2.1.1-1ubuntu1~vivid2 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
2.1.1-1ubuntu1~vivid2 uploaded. I'll upload 2.1.1-1ubuntu1 to wily in a
few minutes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1450642
Title:
seccomp missing many new syscalls
To manage notific
Actually, because that version number, 2.1.1-1ubuntu1~vivid1, has
already been used in wily, we can't use the same version number in
vivid. I'll reject the upload.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Since 2.1.1-1ubuntu1~vivid1 is already in wily, I cannot accept this
into vivid. Can you change the string in wily to not include ~vivid1
please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1450642
This bug was fixed in the package libseccomp - 2.1.1-1ubuntu1~vivid1
---
libseccomp (2.1.1-1ubuntu1~vivid1) vivid-proposed; urgency=medium
* add-finit-module.patch: add finit_module syscalls to x86 and x86-64
syscall tables
* update syscalls for modern kernels (skipping MIPS)
** Changed in: libseccomp (Ubuntu Wily)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1450642
Title:
seccomp missing many new syscalls
To manage notifica
Uploaded the same version to wily (it is in unapproved).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1450642
Title:
seccomp missing many new syscalls
To manage notifications about this bug go to:
** Also affects: libseccomp (Ubuntu Wily)
Importance: Undecided
Assignee: Jamie Strandboge (jdstrand)
Status: In Progress
** Also affects: libseccomp (Ubuntu Vivid)
Importance: Undecided
Status: New
** Changed in: libseccomp (Ubuntu Vivid)
Status: New => In Progres
** Description changed:
- Several syscalls were discovered to be missing when using the launcher
- on snappy. These should be added so we may properly support seccomp
- filtering.
+ [Impact]
+ Several syscalls were discovered to be missing when using the launcher on
snappy. These should be added
31 matches
Mail list logo
