Linux network filesystem support library
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: NeilBrown <neil@brown.name>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>, Jan Kara <jack@suse.cz>,
	 David Howells <dhowells@redhat.com>,
	Chuck Lever <chuck.lever@oracle.com>,
	 Jeff Layton <jlayton@kernel.org>,
	linux-nfs@vger.kernel.org, netfs@lists.linux.dev,
	 linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/6 RFC v2] tidy up various VFS lookup functions
Date: Wed, 19 Mar 2025 09:42:54 +0100	[thread overview]
Message-ID: <20250319-vierbeinig-aufruf-ea327bc39320@brauner> (raw)
In-Reply-To: <20250319031545.2999807-1-neil@brown.name>

On Wed, Mar 19, 2025 at 02:01:31PM +1100, NeilBrown wrote:
> This a revised version of a previous posting.  I have dropped the change
> to some lookup functions to pass a vfsmount.  I have also dropped the

Thank you for compromising! I appreciate it.

> I haven't included changes to afs because there are patches in vfs.all
> which make a lot of changes to lookup in afs.  I think (if they are seen
> as a good idea) these patches should aim to land after the afs patches
> and any further fixup in afs can happen then.

If you're fine with this then I suggest we delay this to v6.16. So I've
moved this to the vfs-6.16.async.dir branch which won't show up in -next
before the v6.15 merge window has concluded. I'm pushing this out now.

  parent reply	other threads:[~2025-03-19  8:42 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-19  3:01 [PATCH 0/6 RFC v2] tidy up various VFS lookup functions NeilBrown
2025-03-19  3:01 ` [PATCH 1/6] VFS: improve interface for lookup_one functions NeilBrown
2025-03-19  8:40   ` Christian Brauner
2025-03-20 10:17   ` Jeff Layton
2025-03-20 14:04   ` David Howells
2025-03-22  0:29     ` Al Viro
2025-03-28  1:18     ` NeilBrown
2025-04-04 13:41       ` Christian Brauner
2025-04-04 13:46         ` Christian Brauner
2025-04-04 23:00           ` NeilBrown
2025-03-22  0:27   ` Al Viro
2025-03-28  1:14     ` NeilBrown
2025-03-19  3:01 ` [PATCH 2/6] nfsd: Use lookup_one() rather than lookup_one_len() NeilBrown
2025-03-19 13:04   ` Chuck Lever
2025-03-20 10:19   ` Jeff Layton
2025-03-19  3:01 ` [PATCH 3/6] cachefiles: " NeilBrown
2025-03-20 10:22   ` Jeff Layton
2025-03-20 12:05     ` Christian Brauner
2025-03-20 13:49       ` David Howells
2025-03-20 14:04         ` Christian Brauner
2025-03-19  3:01 ` [PATCH 4/6] VFS: rename lookup_one_len family to lookup_noperm and remove permission check NeilBrown
2025-03-20 10:29   ` Jeff Layton
2025-03-22  0:34   ` Al Viro
2025-03-28  1:31     ` NeilBrown
2025-03-19  3:01 ` [PATCH 5/6] Use try_lookup_noperm() instead of d_hash_and_lookup() outside of VFS NeilBrown
2025-03-20 10:45   ` Jeff Layton
2025-03-22  0:39   ` Al Viro
2025-03-19  3:01 ` [PATCH 6/6] VFS: change lookup_one_common and lookup_noperm_common to take a qstr NeilBrown
2025-03-20 10:46   ` Jeff Layton
2025-03-19  8:42 ` Christian Brauner [this message]
2025-03-19  9:23   ` [PATCH 0/6 RFC v2] tidy up various VFS lookup functions NeilBrown

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=20250319-vierbeinig-aufruf-ea327bc39320@brauner \
    --to=brauner@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=dhowells@redhat.com \
    --cc=jack@suse.cz \
    --cc=jlayton@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neil@brown.name \
    --cc=netfs@lists.linux.dev \
    --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