seccomp / libseccomp / 857 / 1

89%

main: 90%

push

travis-ci

<a href="https://github.com/seccomp/libseccomp/commit/<a class=hub.com/seccomp/libseccomp/commit/b926e5af7295b04e8cf7ac4929731fed0f53a711">b926e5af7<a href="https://github.com/seccomp/libseccomp/commit/b926e5af7295b04e8cf7ac4929731fed0f53a711">&quot;&gt;system: use old SECCOMP_IOCTL_NOTIF_ID_VALID number if necessary

Kernel commit 47e33c05f9f0 (&amp;quot;seccomp: Fix ioctl number for
SECCOMP_IOCTL_NOTIF_ID_VALID&amp;quot;) changed the public definition of
SECCOMP_IOCTL_NOTIF_ID_VALID for correctness sake because it had the
wrong direction (no current functional change). If libseccomp is built
against kernel headers after this commit but is run on a kernel that was
built prior to this commit, then the ioctl will always return -1 EINVAL
and thus seccomp_notify_id_valid will incorrectly return -ENOENT.

Copy the (now non-public) definition of the old ioctl number and try it
if the ioctl with the number from the kernel headers fails with -1
EINVAL.

Also, update the fallback definition of SECCOMP_IOCTL_NOTIF_ID_VALID to
the new value.

Acked-by: Tom Hromatka &amp;lt;tom.hromatka@oracle.com&amp;gt;
Signed-off-by: Max Rees &amp;lt;maxcrees@me.com&amp;gt;
[PM: tweak some vertical whitespace, subject line]
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/83d7b022fa7ef8c24516cc668efc879e5398403f">83d7b022f</a>">83d7b022f</a><a href="https://github.com/seccomp/libseccomp/commit/b926e5af7295b04e8cf7ac4929731fed0f53a711">)

4370 of 4700 relevant lines covered (92.98%)

241599.18 hits per line