Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
strange behaviour on v4.4 kernels with libseccomp v2.3.1 #40
Comments
added a commit
to xnox/libseccomp
that referenced
this issue
Jun 10, 2016
xnox
referenced this issue
Jun 10, 2016
Closed
Drop table overrides in x86_syscall_resolve_name() to pseudo syscall … #41
xnox
commented
Jun 10, 2016
|
Actually this is maybe a non-bug, given 73d83e4 |
xnox
commented
Jun 10, 2016
•
|
silly me
|
xnox
closed this
Jun 10, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
xnox commentedJun 10, 2016
Hello,
I'm in a i686 chroot, and using scmp_sys_resolver I see multiple regression with syscall look-ups. The tests I run is to check that number->name->number lookups are roundtrip safe, and they appear to not be as per below:
My expectation was for the output to just be:
I see this regression for other syscalls too, on i686 and on s390x architectures.
amd64 and ppc64el pass correctly.
s390x failures:
i686 failures:
Are my expectation somehow wrong? is v4.5 kernel required for v2.3.1 release? Is there a bug in compat between kernel versions?