[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250609005009.GB299672@ZenIV>
Date: Mon, 9 Jun 2025 01:50:09 +0100
From: Al Viro <viro@...iv.linux.org.uk>
To: NeilBrown <neil@...wn.name>
Cc: Christian Brauner <brauner@...nel.org>, Jan Kara <jack@...e.cz>,
Chuck Lever <chuck.lever@...cle.com>,
Jeff Layton <jlayton@...nel.org>,
Amir Goldstein <amir73il@...il.com>,
Jan Harkes <jaharkes@...cmu.edu>,
David Howells <dhowells@...hat.com>, Tyler Hicks <code@...icks.com>,
Miklos Szeredi <miklos@...redi.hu>,
Carlos Maiolino <cem@...nel.org>, linux-fsdevel@...r.kernel.org,
coda@...cmu.edu, codalist@...a.cs.cmu.edu,
linux-nfs@...r.kernel.org, netfs@...ts.linux.dev,
ecryptfs@...r.kernel.org, linux-unionfs@...r.kernel.org,
linux-xfs@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 5/5] Change vfs_mkdir() to unlock on failure.
On Mon, Jun 09, 2025 at 09:09:37AM +1000, NeilBrown wrote:
> Proposed changes to directory-op locking will lock the dentry rather
> than the whole directory. So the dentry will need to be unlocked.
Please, repost your current proposal _before_ that one goes anywhere.
Powered by blists - more mailing lists