From: Al Viro <viro@zeniv.linux.org.uk>
To: Askar Safin <safinaskar@zohomail.com>
Cc: Christian Brauner <brauner@kernel.org>, 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 4/4] vfs: fs/namei.c: if RESOLVE_NO_XDEV passed to openat2, don't *trigger* automounts
Date: Sun, 17 Aug 2025 18:53:19 +0100 [thread overview]
Message-ID: <20250817175319.GY222315@ZenIV> (raw)
In-Reply-To: <20250817171513.259291-5-safinaskar@zohomail.com>
On Sun, Aug 17, 2025 at 05:15:13PM +0000, Askar Safin wrote:
> @@ -1472,6 +1484,10 @@ static int __traverse_mounts(struct path *path, unsigned flags, bool *jumped,
> /* Allow the filesystem to manage the transit without i_rwsem
> * being held. */
> if (flags & DCACHE_MANAGE_TRANSIT) {
> + if (lookup_flags & LOOKUP_NO_XDEV) {
> + ret = -EXDEV;
> + break;
I don't thing it's right in RCU mode, if nothing else...
next prev parent reply other threads:[~2025-08-17 17:53 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 [this message]
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
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=20250817175319.GY222315@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=autofs@vger.kernel.org \
--cc=brauner@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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.