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

[Mateusz Guzik]

On Wed, Jan 14, 2026 at 3:27 AM Lai, Yi <yi1.lai@xxxxxxxxxxxxxxx> wrote:
> I used Syzkaller and found that there is WARNING: bad unlock balance in __wait_on_freeing_inode in linux-next next-20260113.
>
> [   57.741960] -------------------------------------
> [   57.742317] repro/663 is trying to release lock (rcu_read_lock) at:
> [   57.742831] [<ffffffff821343ea>] __wait_on_freeing_inode+0x13a/0x3b0
> [   57.743361] but there are no more locks to release!

uh. I made sure the hash lock dance + retry is fine, I missed the
obvious rcu problem

Figuring out a way to fix it is a matter of taste, so I'm going to
chew on it a little bit.


thanks for the report!