public inbox for v9fs@lists.linux.dev
 help / color / mirror / Atom feed
From: syzbot <syzbot+56bd5818697f0f93fdd9@syzkaller.appspotmail.com>
To: asmadeus@codewreck.org, brauner@kernel.org, dhowells@redhat.com,
	 ericvh@kernel.org, hdanton@sina.com,
	linux-kernel@vger.kernel.org,  linux_oss@crudebyte.com,
	lucho@ionkov.net, max.kellermann@ionos.com,
	 syzkaller-bugs@googlegroups.com, v9fs@lists.linux.dev
Subject: Re: [syzbot] [v9fs?] INFO: task hung in v9fs_evict_inode
Date: Mon, 17 Nov 2025 18:14:02 -0800	[thread overview]
Message-ID: <691bd66a.a70a0220.3124cb.00ae.GAE@google.com> (raw)
In-Reply-To: <6751804a.050a0220.17bd51.009a.GAE@google.com>

syzbot suspects this issue was fixed by commit:

commit 4d428dca252c858bfac691c31fa95d26cd008706
Author: Max Kellermann <max.kellermann@ionos.com>
Date:   Thu Sep 25 13:08:20 2025 +0000

    netfs: fix reference leak

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=1478fb42580000
start commit:   4871b7cb27f4 Merge tag 'v6.16-rc6-smb3-client-fixes' of gi..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=12b5044868deb866
dashboard link: https://syzkaller.appspot.com/bug?extid=56bd5818697f0f93fdd9
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=14d7e38c580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=132ff8f0580000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: netfs: fix reference leak

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

  parent reply	other threads:[~2025-11-18  2:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-05 10:28 [syzbot] [v9fs?] INFO: task hung in v9fs_evict_inode syzbot
2025-05-10 17:00 ` syzbot
2025-11-18  2:14 ` syzbot [this message]
2025-11-18 15:25   ` David Howells
2025-11-18 16:12     ` Max Kellermann
2025-11-18 16:30       ` David Howells
2025-11-18 16:30   ` David Howells

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=691bd66a.a70a0220.3124cb.00ae.GAE@google.com \
    --to=syzbot+56bd5818697f0f93fdd9@syzkaller.appspotmail.com \
    --cc=asmadeus@codewreck.org \
    --cc=brauner@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=ericvh@kernel.org \
    --cc=hdanton@sina.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux_oss@crudebyte.com \
    --cc=lucho@ionkov.net \
    --cc=max.kellermann@ionos.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=v9fs@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox