[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2200414.1763479511@warthog.procyon.org.uk>
Date: Tue, 18 Nov 2025 15:25:11 +0000
From: David Howells <dhowells@...hat.com>
To: syzbot <syzbot+56bd5818697f0f93fdd9@...kaller.appspotmail.com>,
max.kellermann@...os.com
Cc: dhowells@...hat.com, asmadeus@...ewreck.org, brauner@...nel.org,
ericvh@...nel.org, hdanton@...a.com, linux-kernel@...r.kernel.org,
linux_oss@...debyte.com, lucho@...kov.net,
syzkaller-bugs@...glegroups.com, v9fs@...ts.linux.dev
Subject: Re: [syzbot] [v9fs?] INFO: task hung in v9fs_evict_inode
syzbot <syzbot+56bd5818697f0f93fdd9@...kaller.appspotmail.com> wrote:
> syzbot suspects this issue was fixed by commit:
>
> commit 4d428dca252c858bfac691c31fa95d26cd008706
> Author: Max Kellermann <max.kellermann@...os.com>
> Date: Thu Sep 25 13:08:20 2025 +0000
>
> netfs: fix reference leak
> ...
> dashboard link: https://syzkaller.appspot.com/bug?extid=56bd5818697f0f93fdd9
That sounds reasonable. I don't know if Max has a blocked cpu message for
comparison?
David
Powered by blists - more mailing lists