From: Yuntao Wang <yuntao.wang@linux.dev>
To: brauner@kernel.org
Cc: jack@suse.cz, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk,
yuntao.wang@linux.dev
Subject: Re: [PATCH] fs: fix incorrect lflags value in the move_mount syscall
Date: Thu, 14 Aug 2025 09:14:59 +0800 [thread overview]
Message-ID: <20250814011459.270835-1-yuntao.wang@linux.dev> (raw)
In-Reply-To: <20250811-zitat-diebe-3acc89b8c971@brauner>
On Mon, 11 Aug 2025 16:06:59 +0200, Christian Brauner <brauner@kernel.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
next prev parent reply other threads:[~2025-08-14 1:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 5:24 [PATCH] fs: fix incorrect lflags value in the move_mount syscall Yuntao Wang
2025-08-11 14:06 ` Christian Brauner
2025-08-14 1:14 ` Yuntao Wang [this message]
2025-08-11 14:07 ` Christian Brauner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250814011459.270835-1-yuntao.wang@linux.dev \
--to=yuntao.wang@linux.dev \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).