On Thu, 9 Jan 2025 at 18:45, Al Viro <viro@xxxxxxxxxxxxxxxxxx> wrote:
>
> However, to reduce dentry_operations bloat, let's add one method instead -
> ->d_want_unalias(alias, true) instead of ->d_unalias_trylock(alias) and
> ->d_want_unalias(alias, false) instead of ->d_unalias_unlock(alias).
Ugh.
So of all the patches, this is the one that I hate.
I absolutely detest interfaces with random true/false arguments, and
when it is about locking, the "detest" becomes something even darker
and more visceral.
I think it would be a lot better as separate ops, considering that
(a) we'll probably have only one or two actual users, so it's not
like it complicates things on that side
(b) we don't have *that* many "struct dentry_operations" structures:
I think they are all statically generated constant structures
(typically one or two per filesystem), so it's not like we're saving
memory by merging those pointers into one.
Please?
Linus
