Re: [PATCH v2] fs: make insert_inode_locked() wait for inode destruction

[Christian Brauner]

On Wed, Jan 14, 2026 at 10:47:16AM +0100, Mateusz Guzik wrote:
> This is the only routine which instead skipped instead of waiting.
> 
> The current behavior is arguably a bug as it results in a corner case
> where the inode hash can have *two* matching inodes, one of which is on
> its way out.
> 
> Ironing out this difference is an incremental step towards sanitizing
> the API.
> 
> Signed-off-by: Mateusz Guzik <mjguzik@xxxxxxxxx>
> ---

Still reviewing but if ok I'll replace the buggy version.