On Fri, Nov 24, 2023 at 10:20:39AM -0500, Gabriel Krisman Bertazi wrote:
> I'm not sure why it changed. I'm guessing that, since it doesn't make
> sense to set fscrypt_d_revalidate for every dentry in the
> !case-insensitive case, they just kept the same behavior for
> case-insensitive+fscrypt. This is what I get from looking at the git
> history.
>
> I will get a new series reverting to use ->s_d_op, folding the
> dentry_cmp behavior you mentioned, and based on what you merge in your
> branch.
FWIW, I suspect that we might want something along the lines of
d_set_always_valid(dentry)
{
grab ->d_lock
clear DCACHE_OP_REVALIDATE
release ->d_lock
}
to make it possible to suppress ->d_revalidate() for this particular
dentry...
