seccomp / libseccomp / 644

90%

main: 89%

push

travis-ci

<a href="https://github.com/seccomp/libseccomp/commit/<a class=hub.com/seccomp/libseccomp/commit/d1482eaf5a3643f73bc7f599876e7000c502b3d5">d1482eaf5<a href="https://github.com/seccomp/libseccomp/commit/d1482eaf5a3643f73bc7f599876e7000c502b3d5">&quot;&gt;arch: ensure we don&amp;#39;t &amp;quot;munge&amp;quot; pseudo syscall numbers

A number of arches/ABIs have either syscall offsets (the MIPS
family) or specific bits (x32) which are applied to their normal
syscall numbers.  We generally handle that via &amp;quot;munging&amp;quot; in
libseccomp, and it works reasonably well.  Unfortunately we were
applying this munging process to the negative pseudo syscall
numbers as well and this was causing problems.

This patch fixes the various offset/bit arches/ABIs by not applying
the munging to the negative pseudo syscall numbers.

This resolves GH issue #284:
* https://github.com/seccomp/libseccomp/issues/284

Reported-by: Harald van Dijk &amp;lt;harald@gigawatt.nl&amp;gt;
Acked-by: Tom Hromatka &amp;lt;tom.hromatka@oracle.com&amp;gt;
Signed-off-by: Paul Moore &lt;paul@paul-moore.com&gt;
(imported from commit </a><a class="double-link" href="https://github.com/seccomp/libseccomp/commit/<a class="double-link" href="https://github.com/seccomp/libseccomp/commit/34cde704979defcbddb8eea64295acf0e477c250">34cde7049</a>">34cde7049</a><a href="https://github.com/seccomp/libseccomp/commit/d1482eaf5a3643f73bc7f599876e7000c502b3d5">)

4370 of 4697 relevant lines covered (93.04%)

241772.2 hits per line