So to summarize: in zesty, artful `scmp_sys_resolver -a x86 socket` will return: `-101`. The syscalls are still there in the kernel and libc its just that libseccomp reports a pseudo number again (which it did not in xenial).
The reason why we are seeing negative syscall numbers from libseccomp again is: https://github.com/seccomp/libseccomp/commit/73d83e45efbe8c31067c97155162f17ca51b7435 The interessting question is what we should do - the most simple answer is to just revert this, this would be consistent with xenial. But given that its an upstream commit I'm hesitant to do this. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
