From: syzbot <syzbot+5216036fc59c43d1ee02@syzkaller.appspotmail.com>
To: Yuezhang.Mo@sony.com, brauner@kernel.org, jack@suse.cz,
linkinjeon@kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, sj1557.seo@samsung.com,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk,
yuezhang.mo@sony.com
Subject: Re: [syzbot] [exfat?] WARNING in __rt_mutex_slowlock_locked (2)
Date: Fri, 07 Nov 2025 01:11:03 -0800 [thread overview]
Message-ID: <690db7a7.a70a0220.22f260.002e.GAE@google.com> (raw)
In-Reply-To: <690d2bd5.a70a0220.22f260.000f.GAE@google.com>
syzbot has bisected this issue to:
commit 184fa506e392eb78364d9283c961217ff2c0617b
Author: Yuezhang Mo <Yuezhang.Mo@sony.com>
Date: Mon Oct 28 03:23:36 2024 +0000
exfat: fix out-of-bounds access of directory entries
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12217812580000
start commit: c2c2ccfd4ba7 Merge tag 'net-6.18-rc5' of git://git.kernel...
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=11217812580000
console output: https://syzkaller.appspot.com/x/log.txt?x=16217812580000
kernel config: https://syzkaller.appspot.com/x/.config?x=41ad820f608cb833
dashboard link: https://syzkaller.appspot.com/bug?extid=5216036fc59c43d1ee02
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11062a58580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16e19084580000
Reported-by: syzbot+5216036fc59c43d1ee02@syzkaller.appspotmail.com
Fixes: 184fa506e392 ("exfat: fix out-of-bounds access of directory entries")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-11-07 9:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 23:14 [syzbot] [exfat?] WARNING in __rt_mutex_slowlock_locked (2) syzbot
2025-11-07 7:29 ` Namjae Jeon
2025-11-07 8:29 ` syzbot
2025-11-07 9:11 ` syzbot [this message]
2025-11-08 11:06 ` Namjae Jeon
2025-11-08 11:46 ` syzbot
2025-11-12 3:37 ` Namjae Jeon
2025-11-12 4:07 ` syzbot
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=690db7a7.a70a0220.22f260.002e.GAE@google.com \
--to=syzbot+5216036fc59c43d1ee02@syzkaller.appspotmail.com \
--cc=Yuezhang.Mo@sony.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sj1557.seo@samsung.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).