[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250222045636.GP1977892@ZenIV>
Date: Sat, 22 Feb 2025 04:56:36 +0000
From: Al Viro <viro@...iv.linux.org.uk>
To: NeilBrown <neilb@...e.de>
Cc: Christian Brauner <brauner@...nel.org>, Jan Kara <jack@...e.cz>,
Miklos Szeredi <miklos@...redi.hu>, Xiubo Li <xiubli@...hat.com>,
Ilya Dryomov <idryomov@...il.com>,
Richard Weinberger <richard@....at>,
Anton Ivanov <anton.ivanov@...bridgegreys.com>,
Johannes Berg <johannes@...solutions.net>,
Trond Myklebust <trondmy@...nel.org>,
Anna Schumaker <anna@...nel.org>,
Chuck Lever <chuck.lever@...cle.com>,
Jeff Layton <jlayton@...nel.org>,
Olga Kornievskaia <okorniev@...hat.com>,
Dai Ngo <Dai.Ngo@...cle.com>, Tom Talpey <tom@...pey.com>,
Sergey Senozhatsky <senozhatsky@...omium.org>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-cifs@...r.kernel.org, linux-nfs@...r.kernel.org,
linux-um@...ts.infradead.org, ceph-devel@...r.kernel.org,
netfs@...ts.linux.dev
Subject: Re: [PATCH 1/6] Change inode_operations.mkdir to return struct
dentry *
On Fri, Feb 21, 2025 at 10:36:30AM +1100, NeilBrown wrote:
> Not all filesystems reliably result in a positive hashed dentry:
>
> - NFS, cifs, hostfs will sometimes need to perform a lookup of
> the name to get inode information. Races could result in this
> returning something different. Note that this lookup is
> non-atomic which is what we are trying to avoid. Placing the
> lookup in filesystem code means it only happens when the filesystem
> has no other option.
At least in case of cifs I don't see that lookup anywhere in your
series. Have I missed it, or...?
Powered by blists - more mailing lists