fork: allow CLONE_NEWTIME in clone3 flags
authorTobias Klauser <tklauser@distanz.ch>
Wed, 8 Mar 2023 10:51:26 +0000 (11:51 +0100)
committerChristian Brauner (Microsoft) <brauner@kernel.org>
Wed, 8 Mar 2023 11:31:34 +0000 (12:31 +0100)
commita402f1e35313fc7ce2ca60f543c4402c2c7c3544
tree9de4756376f8c5d9a4d3999b830ca3ac8901415b
parentfe15c26ee26efa11741a7b632e9f23b01aca4cc6
fork: allow CLONE_NEWTIME in clone3 flags

Currently, calling clone3() with CLONE_NEWTIME in clone_args->flags
fails with -EINVAL. This is because CLONE_NEWTIME intersects with
CSIGNAL. However, CSIGNAL was deprecated when clone3 was introduced in
commit 7f192e3cd316 ("fork: add clone3"), allowing re-use of that part
of clone flags.

Fix this by explicitly allowing CLONE_NEWTIME in clone3_args_valid. This
is also in line with the respective check in check_unshare_flags which
allow CLONE_NEWTIME for unshare().

Fixes: 769071ac9f20 ("ns: Introduce Time Namespace")
Cc: Andrey Vagin <avagin@openvz.org>
Cc: Christian Brauner <brauner@kernel.org>
Cc: stable@vger.kernel.org
Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Reviewed-by: Christian Brauner <brauner@kernel.org>
Signed-off-by: Christian Brauner (Microsoft) <brauner@kernel.org>
kernel/fork.c