Received-SPF: pass (google.com: domain of linux-kernel+bounces-46523-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:40f1:3f00::1 as permitted sender) client-ip=2604:1380:40f1:3f00::1;
From: Christian Brauner <brauner@kernel.org>
To: Wang Jinchao <wangjinchao@xfusion.com>
Cc: Christian Brauner <brauner@kernel.org>,
	stone.xulei@xfusion.com,
	viro@zeniv.linux.org.uk,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fork: Using clone_flags for legacy clone check
Date: Wed, 31 Jan 2024 14:42:10 +0100
Message-ID: <20240131-skeptiker-bahnstation-a6bc73ed780e@brauner>
In-Reply-To: <202401311054+0800-wangjinchao@xfusion.com>
References: <202401311054+0800-wangjinchao@xfusion.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

On Wed, 31 Jan 2024 10:54:41 +0800, Wang Jinchao wrote:
> In the current implementation of clone(), there is a line that
> initializes `u64 clone_flags = args->flags` at the top.
> This means that there is no longer a need to use args->flags
> for the legacy clone check.
> 
> 

Applied to the vfs.misc branch of the vfs/vfs.git tree.
Patches in the vfs.misc branch should appear in linux-next soon.

Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.

It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.

Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.misc

[1/1] fork: Using clone_flags for legacy clone check
      https://git.kernel.org/vfs/vfs/c/b473491b6cf8