seccomp: Fix ioctl number for SECCOMP_IOCTL_NOTIF_ID_VALID
authorKees Cook <keescook@chromium.org>
Mon, 15 Jun 2020 22:42:46 +0000 (15:42 -0700)
committerKees Cook <keescook@chromium.org>
Fri, 10 Jul 2020 23:01:52 +0000 (16:01 -0700)
commit47e33c05f9f07cac3de833e531bcac9ae052c7ca
tree1913290075b6efe5174e4843fd42224316e59be1
parent279ed8900079831ba436007dbc5e24530f026ce2
seccomp: Fix ioctl number for SECCOMP_IOCTL_NOTIF_ID_VALID

When SECCOMP_IOCTL_NOTIF_ID_VALID was first introduced it had the wrong
direction flag set. While this isn't a big deal as nothing currently
enforces these bits in the kernel, it should be defined correctly. Fix
the define and provide support for the old command until it is no longer
needed for backward compatibility.

Fixes: 6a21cc50f0c7 ("seccomp: add a return code to trap to userspace")
Signed-off-by: Kees Cook <keescook@chromium.org>
include/uapi/linux/seccomp.h
kernel/seccomp.c
tools/testing/selftests/seccomp/seccomp_bpf.c