From: Christian Brauner <brauner@kernel.org>
To: Askar Safin <safinaskar@zohomail.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>, Jan Kara <jack@suse.cz>,
cyphar@cyphar.com, Ian Kent <raven@themaw.net>,
linux-fsdevel@vger.kernel.org,
David Howells <dhowells@redhat.com>,
autofs mailing list <autofs@vger.kernel.org>,
patches@lists.linux.dev
Subject: Re: [PATCH 0/4] vfs: if RESOLVE_NO_XDEV passed to openat2, don't *trigger* automounts
Date: Tue, 19 Aug 2025 10:24:22 +0200 [thread overview]
Message-ID: <20250819-handlanger-explizit-b0a0debe7bc6@brauner> (raw)
In-Reply-To: <20250817171513.259291-1-safinaskar@zohomail.com>
On Sun, Aug 17, 2025 at 05:15:09PM +0000, Askar Safin wrote:
> openat2 had a bug: if we pass RESOLVE_NO_XDEV, then openat2
> doesn't traverse through automounts, but may still trigger them.
> See this link for full bug report with reproducer:
> https://lore.kernel.org/linux-fsdevel/20250817075252.4137628-1-safinaskar@zohomail.com/
>
> This patchset fixes the bug.
Thanks, this looks all sane. Once you've addressed all comments I'll get
this into -next.
> RESOLVE_NO_XDEV logic hopefully becomes more clear:
> now we immediately fail when we cross mountpoints.
>
> I think this patchset should get to -fixes and stable trees.
>
> I split everything to very small commits to make
> everything as bisectable as possible.
Thanks! But as said ealier in the thread folding the first three
preparatory patches is fine.
>
> Minimal testing was performed. I tested that my original
> reproducer doesn't reproduce anymore. And I did boot-test
> with localmodconfig in qemu
>
> I'm not very attached to this patchset. I. e. I will not be offended
> if someone else will submit different fix for this bug.
>
> Askar Safin (4):
> vfs: fs/namei.c: move cross-device check to traverse_mounts
> vfs: fs/namei.c: remove LOOKUP_NO_XDEV check from handle_mounts
> vfs: fs/namei.c: move cross-device check to __traverse_mounts
> vfs: fs/namei.c: if RESOLVE_NO_XDEV passed to openat2, don't *trigger*
> automounts
>
> fs/namei.c | 29 +++++++++++++++++++++++------
> 1 file changed, 23 insertions(+), 6 deletions(-)
>
> --
> 2.47.2
>
next prev parent reply other threads:[~2025-08-19 8:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-17 17:15 [PATCH 0/4] vfs: if RESOLVE_NO_XDEV passed to openat2, don't *trigger* automounts Askar Safin
2025-08-17 17:15 ` [PATCH 1/4] vfs: fs/namei.c: move cross-device check to traverse_mounts Askar Safin
2025-08-17 17:15 ` [PATCH 2/4] vfs: fs/namei.c: remove LOOKUP_NO_XDEV check from handle_mounts Askar Safin
2025-08-17 18:00 ` Al Viro
2025-08-17 17:15 ` [PATCH 3/4] vfs: fs/namei.c: move cross-device check to __traverse_mounts Askar Safin
2025-08-17 17:15 ` [PATCH 4/4] vfs: fs/namei.c: if RESOLVE_NO_XDEV passed to openat2, don't *trigger* automounts Askar Safin
2025-08-17 17:53 ` Al Viro
2025-08-17 17:54 ` Al Viro
2025-08-18 5:17 ` Aleksa Sarai
2025-08-18 7:15 ` Aleksa Sarai
2025-08-25 17:48 ` Askar Safin
2025-08-18 5:31 ` [PATCH 0/4] vfs: " Aleksa Sarai
2025-08-19 8:21 ` Christian Brauner
2025-08-25 12:46 ` Askar Safin
2025-08-25 13:14 ` Christian Brauner
2025-08-19 8:24 ` Christian Brauner [this message]
2025-08-20 18:04 ` Askar Safin
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=20250819-handlanger-explizit-b0a0debe7bc6@brauner \
--to=brauner@kernel.org \
--cc=autofs@vger.kernel.org \
--cc=cyphar@cyphar.com \
--cc=dhowells@redhat.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=patches@lists.linux.dev \
--cc=raven@themaw.net \
--cc=safinaskar@zohomail.com \
--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