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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAGudoHHYTP7vwOMG5R1L_TDMrHkD01QjJxK5JitEMigccbOXJw@mail.gmail.com>
Date: Wed, 14 Jan 2026 10:11:40 +0100
From: Mateusz Guzik <mjguzik@...il.com>
To: "Lai, Yi" <yi1.lai@...ux.intel.com>
Cc: brauner@...nel.org, viro@...iv.linux.org.uk, jack@...e.cz, 
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH] fs: make insert_inode_locked() wait for inode destruction

On Wed, Jan 14, 2026 at 3:27 AM Lai, Yi <yi1.lai@...ux.intel.com> 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!