From: syzbot <syzbot+73c8cd74d6440aef4d6a@syzkaller.appspotmail.com>
To: Yuezhang.Mo@sony.com, andy.wu@sony.com, bp@alien8.de,
dave.hansen@linux.intel.com, hpa@zytor.com,
linkinjeon@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, wataru.aoyama@sony.com, x86@kernel.org,
yuezhang.mo@sony.com
Subject: Re: [syzbot] [exfat?] INFO: task hung in exfat_lookup (3)
Date: Wed, 05 Feb 2025 15:08:04 -0800 [thread overview]
Message-ID: <67a3ef54.050a0220.19061f.05f1.GAE@google.com> (raw)
In-Reply-To: <6770ec42.050a0220.2f3838.04a5.GAE@google.com>
syzbot suspects this issue was fixed by commit:
commit a5324b3a488d883aa2d42f72260054e87d0940a0
Author: Yuezhang Mo <Yuezhang.Mo@sony.com>
Date: Mon Dec 16 05:39:42 2024 +0000
exfat: fix the infinite loop in __exfat_free_cluster()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15ab01b0580000
start commit: 9b2ffa6148b1 Merge tag 'mtd/fixes-for-6.13-rc5' of git://g..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=4c4096b0d467a682
dashboard link: https://syzkaller.appspot.com/bug?extid=73c8cd74d6440aef4d6a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=101d6adf980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11d100b0580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: exfat: fix the infinite loop in __exfat_free_cluster()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-02-05 23:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-29 6:29 [syzbot] [exfat?] INFO: task hung in exfat_lookup (3) syzbot
2025-02-05 23:08 ` 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=67a3ef54.050a0220.19061f.05f1.GAE@google.com \
--to=syzbot+73c8cd74d6440aef4d6a@syzkaller.appspotmail.com \
--cc=Yuezhang.Mo@sony.com \
--cc=andy.wu@sony.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linkinjeon@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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox