lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250814011459.270835-1-yuntao.wang@linux.dev>
Date: Thu, 14 Aug 2025 09:14:59 +0800
From: Yuntao Wang <yuntao.wang@...ux.dev>
To: brauner@...nel.org
Cc: jack@...e.cz,
	linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	viro@...iv.linux.org.uk,
	yuntao.wang@...ux.dev
Subject: Re: [PATCH] fs: fix incorrect lflags value in the move_mount syscall

On Mon, 11 Aug 2025 16:06:59 +0200, Christian Brauner <brauner@...nel.org> wrote:

> On Mon, 11 Aug 2025 13:24:26 +0800, Yuntao Wang wrote:
> > The lflags value used to look up from_path was overwritten by the one used
> > to look up to_path.
> > 
> > In other words, from_path was looked up with the wrong lflags value. Fix it.
> > 
> > 
> 
> Applied to the vfs.fixes branch of the vfs/vfs.git tree.
> Patches in the vfs.fixes 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.fixes
> 
> [1/1] fs: fix incorrect lflags value in the move_mount syscall
>       https://git.kernel.org/vfs/vfs/c/593d9e4c3d63

Hi Christian,

It seems the patch hasn't been applied to the vfs.fixes branch, the relevant
code there appears unchanged.

Thanks,
Yuntao

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ