Re: [PATCH v2 0/4] VFS: prepare for changes to directory locking

On Thu, 23 Jul 2026, NeilBrown wrote:
> Thanks a lot to Christian for the review.  I have address all this
> issues found.

Hi,
 has anyone had a chance to review?  Is there any change this could land
 in the next -rc1 ??

Thanks,
NeilBrown


>=20
> Original intro, slightly modified:
>=20
> These patches are part of some prep work to allow changes to directory
> locking.
> The short term goal is to invert the locking order between d_alloc_parallel=
()=20
> and inode_lock() so that d_alloc_parallel() can (only) be called without
> holding inode_lock().  This particularly requires filesystems not to use=20
> d_drop() in the middle of an operation, which particularly requires the d_s=
plice_alias()
> change.
>=20
> As it will require d_alloc_parallel() to NOT be called under the inode
> lock, d_alloc_trylock() is added which CAN be used when failure is safe
> (dcache priming in readdir).
>=20
> Once these land upstream I can submit patches to various filesystems to
> make use of them.  Then when filesystems are ready I can continue the
> VFS changes.
>=20
> Thanks,
> NeilBrown
>=20
>=20
>  [PATCH v2 1/4] VFS: fix various typos in documentation for
>  [PATCH v2 2/4] VFS: enhance d_splice_alias() to handle hashed
>  [PATCH v2 3/4] VFS: introduce d_alloc_trylock()
>  [PATCH v2 4/4] VFS: add d_duplicate()
>=20
>=20