I'll take a look at this. I'll try an updated libseccomp with xenial's
glibc and a > 4.2 kernel and if this works, I'll pursue an SRU. Is there
a simple test case or snap that I can use to verify it is broken with
old seccomp and working with new?
** Changed in: libseccomp (Ubuntu)
Importance: Undecided => High
** Changed in: libseccomp (Ubuntu)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
** Changed in: libseccomp (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576066
Title:
32bit glibc calls old socketcall() syscall, causing seccomp problems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1576066/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
