From: syzbot <syzbot+6983c03a6a28616e362f@syzkaller.appspotmail.com>
To: Yuezhang.Mo@sony.com, andy.wu@sony.com, bp@alien8.de,
brauner@kernel.org, dave.hansen@linux.intel.com, hpa@zytor.com,
jack@suse.cz, kent.overstreet@linux.dev, linkinjeon@kernel.org,
linux-bcachefs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, mingo@redhat.com,
sj1557.seo@samsung.com, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, viro@zeniv.linux.org.uk,
wataru.aoyama@sony.com, x86@kernel.org, yuezhang.mo@sony.com
Subject: Re: [syzbot] [bcachefs?] INFO: task hung in vfs_unlink (5)
Date: Sun, 20 Apr 2025 14:12:03 -0700 [thread overview]
Message-ID: <68056323.050a0220.243d89.0036.GAE@google.com> (raw)
In-Reply-To: <674db1c7.050a0220.ad585.0051.GAE@google.com>
syzbot suspects this issue was fixed by commit:
commit b0522303f67255926b946aa66885a0104d1b2980
Author: Yuezhang Mo <Yuezhang.Mo@sony.com>
Date: Mon Mar 17 02:53:10 2025 +0000
exfat: fix the infinite loop in exfat_find_last_cluster()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=155b4c70580000
start commit: bb2281fb05e5 Merge tag 'x86_microcode_for_v6.14_rc6' of gi..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=523d3ff8e053340a
dashboard link: https://syzkaller.appspot.com/bug?extid=6983c03a6a28616e362f
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12cf7078580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10197da8580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: exfat: fix the infinite loop in exfat_find_last_cluster()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-04-20 21:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 13:10 [syzbot] [bcachefs?] INFO: task hung in vfs_unlink (5) syzbot
2025-03-06 9:21 ` syzbot
2025-03-06 17:09 ` syzbot
2025-04-20 21:12 ` syzbot [this message]
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=68056323.050a0220.243d89.0036.GAE@google.com \
--to=syzbot+6983c03a6a28616e362f@syzkaller.appspotmail.com \
--cc=Yuezhang.Mo@sony.com \
--cc=andy.wu@sony.com \
--cc=bp@alien8.de \
--cc=brauner@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jack@suse.cz \
--cc=kent.overstreet@linux.dev \
--cc=linkinjeon@kernel.org \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sj1557.seo@samsung.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--cc=wataru.aoyama@sony.com \
--cc=x86@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.