[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230323143320.GC136146@mit.edu>
Date: Thu, 23 Mar 2023 10:33:20 -0400
From: "Theodore Ts'o" <tytso@....edu>
To: Gabriel Krisman Bertazi <krisman@...labora.com>
Cc: viro@...iv.linux.org.uk, jaegeuk@...nel.org, ebiggers@...nel.org,
linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org,
linux-f2fs-devel@...ts.sourceforge.net, kernel@...labora.com
Subject: Re: [PATCH 1/7] fs: Expose name under lookup to d_revalidate hook
On Wed, Jun 22, 2022 at 03:45:57PM -0400, Gabriel Krisman Bertazi wrote:
> Negative dentries support on case-insensitive ext4/f2fs will require
> access to the name under lookup to ensure it matches the dentry. This
> adds an optional new flavor of cached dentry revalidation hook to expose
> this extra parameter.
>
> I'm fine with extending d_revalidate instead of adding a new hook, if
> it is considered cleaner and the approach is accepted. I wrote a new
> hook to simplify reviewing.
>
> Signed-off-by: Gabriel Krisman Bertazi <krisman@...labora.com>
Reviewed-by: Theodore Ts'o <tytso@....edu>
Al, could you take a look and see if you have any objections?
Also, any thoughts about adding the new d_revalidate_name() callback
as opposed to change d_revalidate() to add an extra parameter? It
looks like there are some 33 d_revalidate callbacks, from 24 file
sysetms, that would have to be changed.
Cheers,
- Ted
Powered by blists - more mailing lists