[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKPOu+-da_s=r2-1WynNkg024uxFE2PEHTp=9_uJP97fskvQyA@mail.gmail.com>
Date: Tue, 18 Nov 2025 17:12:53 +0100
From: Max Kellermann <max.kellermann@...os.com>
To: David Howells <dhowells@...hat.com>
Cc: syzbot <syzbot+56bd5818697f0f93fdd9@...kaller.appspotmail.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
On Tue, Nov 18, 2025 at 4:25 PM David Howells <dhowells@...hat.com> wrote:
>
> 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?
Indeed, that's the same symptom I had; my patch is the fix.
Unfortunately, I don't keep any of the debugging output - I should
have added that to the patch description.
Powered by blists - more mailing lists