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)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 19 Aug 2020 06:23:32 +0000 (08:23 +0200)
commitb31507ed228f1716fd8a9f5f0924037fb9dd9741
treecc909c66b7ac9bd405cd136436b939784e6fce29
parent3667a66c7caeef43d5bff034ce3d499b8c80a7f9
seccomp: Fix ioctl number for SECCOMP_IOCTL_NOTIF_ID_VALID

[ Upstream commit 47e33c05f9f07cac3de833e531bcac9ae052c7ca ]

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>
Signed-off-by: Sasha Levin <sashal@kernel.org>
include/uapi/linux/seccomp.h
kernel/seccomp.c
tools/testing/selftests/seccomp/seccomp_bpf.c