From: Jeff Layton <jlayton@kernel.org>
To: NeilBrown <neil@brown.name>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Chuck Lever <chuck.lever@oracle.com>,
Alexander Aring <alex.aring@gmail.com>,
Trond Myklebust <trondmy@kernel.org>,
Anna Schumaker <anna@kernel.org>,
Steve French <sfrench@samba.org>,
Paulo Alcantara <pc@manguebit.org>,
Ronnie Sahlberg <ronniesahlberg@gmail.com>,
Shyam Prasad N <sprasad@microsoft.com>,
Tom Talpey <tom@talpey.com>,
Bharath SM <bharathsm@microsoft.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
David Howells <dhowells@redhat.com>,
Tyler Hicks <code@tyhicks.com>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <Dai.Ngo@oracle.com>,
Amir Goldstein <amir73il@gmail.com>,
Namjae Jeon <linkinjeon@kernel.org>,
Steve French <smfrench@gmail.com>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Carlos Maiolino <cem@kernel.org>,
Kuniyuki Iwashima <kuniyu@google.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-nfs@vger.kernel.org, linux-cifs@vger.kernel.org,
samba-technical@lists.samba.org, netfs@lists.linux.dev,
ecryptfs@vger.kernel.org, linux-unionfs@vger.kernel.org,
linux-xfs@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v4 10/17] vfs: make vfs_create break delegations on parent directory
Date: Mon, 03 Nov 2025 19:30:57 -0500 [thread overview]
Message-ID: <6021e64ed25c3b3e7880f17accb0f7a7b89fac0e.camel@kernel.org> (raw)
In-Reply-To: <176221525113.1793333.253208063990645256@noble.neil.brown.name>
On Tue, 2025-11-04 at 11:14 +1100, NeilBrown wrote:
> On Mon, 03 Nov 2025, Jeff Layton wrote:
> > In order to add directory delegation support, we need to break
> > delegations on the parent whenever there is going to be a change in the
> > directory.
> >
> > Add a delegated_inode parameter to struct createdata. Most callers just
> > leave that as a NULL pointer, but do_mknodat() is changed to wait for a
> > delegation break if there is one.
> >
> > Signed-off-by: Jeff Layton <jlayton@kernel.org>
> > ---
> > fs/namei.c | 26 +++++++++++++++++---------
> > include/linux/fs.h | 2 +-
> > 2 files changed, 18 insertions(+), 10 deletions(-)
> >
> > diff --git a/fs/namei.c b/fs/namei.c
> > index fdf4e78cd041de8c564b7d1d89a46ba2aaf79d53..e8973000a312fb05ebb63a0d9bd83b9a5f8f805d 100644
> > --- a/fs/namei.c
> > +++ b/fs/namei.c
> > @@ -3487,6 +3487,9 @@ int vfs_create(struct createdata *args)
> >
> > mode = vfs_prepare_mode(idmap, dir, mode, S_IALLUGO, S_IFREG);
> > error = security_inode_create(dir, dentry, mode);
> > + if (error)
> > + return error;
> > + error = try_break_deleg(dir, args->delegated_inode);
> > if (error)
> > return error;
> > error = dir->i_op->create(idmap, dir, dentry, mode, args->excl);
> > @@ -4359,6 +4362,8 @@ static int may_mknod(umode_t mode)
> > static int do_mknodat(int dfd, struct filename *name, umode_t mode,
> > unsigned int dev)
> > {
> > + struct delegated_inode delegated_inode = { };
> > + struct createdata cargs = { };
>
> If we must have 'createdata', can it have a 'struct delegated_inode'
> rather than a pointer to it?
>
If we do that, then we'd need some way to signal that the caller
doesn't want to wait on the delegation break. Currently that's
indicated by setting cargs.delegated_inode to NULL. I suppose we could
add a bool for this or something.
I confess that I too am lukewarm on struct createdata. I can live with
it, but it's not clearly a win to me either.
Christian, thoughts?
>
> > struct mnt_idmap *idmap;
> > struct dentry *dentry;
> > struct path path;
> > @@ -4383,18 +4388,16 @@ static int do_mknodat(int dfd, struct filename *name, umode_t mode,
> > switch (mode & S_IFMT) {
> > case 0:
> > case S_IFREG:
> > - {
> > - struct createdata args = { .idmap = idmap,
> > - .dir = path.dentry->d_inode,
> > - .dentry = dentry,
> > - .mode = mode,
> > - .excl = true };
> > -
> > - error = vfs_create(&args);
> > + cargs.idmap = idmap,
> > + cargs.dir = path.dentry->d_inode,
> > + cargs.dentry = dentry,
> > + cargs.delegated_inode = &delegated_inode;
> > + cargs.mode = mode,
> > + cargs.excl = true,
> > + error = vfs_create(&cargs);
> > if (!error)
> > security_path_post_mknod(idmap, dentry);
> > break;
> > - }
> > case S_IFCHR: case S_IFBLK:
> > error = vfs_mknod(idmap, path.dentry->d_inode,
> > dentry, mode, new_decode_dev(dev));
> > @@ -4406,6 +4409,11 @@ static int do_mknodat(int dfd, struct filename *name, umode_t mode,
> > }
> > out2:
> > end_creating_path(&path, dentry);
> > + if (is_delegated(&delegated_inode)) {
> > + error = break_deleg_wait(&delegated_inode);
> > + if (!error)
> > + goto retry;
> > + }
> > if (retry_estale(error, lookup_flags)) {
> > lookup_flags |= LOOKUP_REVAL;
> > goto retry;
> > diff --git a/include/linux/fs.h b/include/linux/fs.h
> > index b61873767b37591aecadd147623d7dfc866bef82..cfcb20a7c4ce4b6dcec98b3eccbdb5ec8bab6fa9 100644
> > --- a/include/linux/fs.h
> > +++ b/include/linux/fs.h
> > @@ -2116,12 +2116,12 @@ struct createdata {
> > struct mnt_idmap *idmap; // idmap of the mount the inode was found from
> > struct inode *dir; // inode of parent directory
> > struct dentry *dentry; // dentry of the child file
> > + struct delegated_inode *delegated_inode; // returns parent inode, if delegated
> > umode_t mode; // mode of the child file
> > bool excl; // whether the file must not yet exist
> > };
> >
> > int vfs_create(struct createdata *);
> > -
> > struct dentry *vfs_mkdir(struct mnt_idmap *, struct inode *,
> > struct dentry *, umode_t, struct delegated_inode *);
> > int vfs_mknod(struct mnt_idmap *, struct inode *, struct dentry *,
> >
> > --
> > 2.51.1
> >
> >
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2025-11-04 0:31 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 12:52 [PATCH v4 00/17] vfs: recall-only directory delegations for knfsd Jeff Layton
2025-11-03 12:52 ` [PATCH v4 01/17] filelock: make lease_alloc() take a flags argument Jeff Layton
2025-11-03 12:52 ` [PATCH v4 02/17] filelock: rework the __break_lease API to use flags Jeff Layton
2025-11-03 12:52 ` [PATCH v4 03/17] filelock: add struct delegated_inode Jeff Layton
2025-11-05 12:19 ` Christian Brauner
2025-11-03 12:52 ` [PATCH v4 04/17] filelock: push the S_ISREG check down to ->setlease handlers Jeff Layton
2025-11-03 12:52 ` [PATCH v4 05/17] vfs: add try_break_deleg calls for parents to vfs_{link,rename,unlink} Jeff Layton
2025-11-03 12:52 ` [PATCH v4 06/17] vfs: allow mkdir to wait for delegation break on parent Jeff Layton
2025-11-03 12:52 ` [PATCH v4 07/17] vfs: allow rmdir " Jeff Layton
2025-11-03 12:52 ` [PATCH v4 08/17] vfs: break parent dir delegations in open(..., O_CREAT) codepath Jeff Layton
2025-11-03 12:52 ` [PATCH v4 09/17] vfs: add struct createdata for passing arguments to vfs_create() Jeff Layton
2025-11-04 0:06 ` NeilBrown
2025-11-04 0:34 ` NeilBrown
2025-11-03 12:52 ` [PATCH v4 10/17] vfs: make vfs_create break delegations on parent directory Jeff Layton
2025-11-04 0:14 ` NeilBrown
2025-11-04 0:30 ` Jeff Layton [this message]
2025-11-05 12:15 ` Christian Brauner
2025-11-04 17:38 ` Simon Horman
2025-11-04 18:10 ` Jeff Layton
2025-11-03 12:52 ` [PATCH v4 11/17] vfs: make vfs_mknod " Jeff Layton
2025-11-03 12:52 ` [PATCH v4 12/17] vfs: make vfs_symlink break delegations on parent dir Jeff Layton
2025-11-03 12:52 ` [PATCH v4 13/17] filelock: lift the ban on directory leases in generic_setlease Jeff Layton
2025-11-03 12:52 ` [PATCH v4 14/17] nfsd: allow filecache to hold S_IFDIR files Jeff Layton
2025-11-03 12:52 ` [PATCH v4 15/17] nfsd: allow DELEGRETURN on directories Jeff Layton
2025-11-03 12:52 ` [PATCH v4 16/17] nfsd: wire up GET_DIR_DELEGATION handling Jeff Layton
2025-11-03 12:52 ` [PATCH v4 17/17] vfs: expose delegation support to userland Jeff Layton
2025-11-03 13:13 ` Jeff Layton
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=6021e64ed25c3b3e7880f17accb0f7a7b89fac0e.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=alex.aring@gmail.com \
--cc=amir73il@gmail.com \
--cc=anna@kernel.org \
--cc=bharathsm@microsoft.com \
--cc=brauner@kernel.org \
--cc=cem@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=code@tyhicks.com \
--cc=dakr@kernel.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=ecryptfs@vger.kernel.org \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=horms@kernel.org \
--cc=jack@suse.cz \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=neil@brown.name \
--cc=netdev@vger.kernel.org \
--cc=netfs@lists.linux.dev \
--cc=okorniev@redhat.com \
--cc=pabeni@redhat.com \
--cc=pc@manguebit.org \
--cc=rafael@kernel.org \
--cc=ronniesahlberg@gmail.com \
--cc=samba-technical@lists.samba.org \
--cc=senozhatsky@chromium.org \
--cc=sfrench@samba.org \
--cc=smfrench@gmail.com \
--cc=sprasad@microsoft.com \
--cc=tom@talpey.com \
--cc=trondmy@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).