From: syzbot <syzbot+list913c0c36c9616478c625@syzkaller.appspotmail.com>
To: linkinjeon@kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, sj1557.seo@samsung.com,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly exfat report (Apr 2026)
Date: Wed, 15 Apr 2026 05:39:26 -0700 [thread overview]
Message-ID: <69df86fe.a70a0220.7fc2.0000.GAE@google.com> (raw)
Hello exfat maintainers/developers,
This is a 31-day syzbot report for the exfat subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/exfat
During the period, 0 new issues were detected and 0 were fixed.
In total, 10 issues are still open and 42 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 3041 Yes possible deadlock in filemap_fault
https://syzkaller.appspot.com/bug?extid=7736960b837908f3a81d
<2> 907 Yes WARNING in rcu_sync_dtor (2)
https://syzkaller.appspot.com/bug?extid=823cd0d24881f21ab9f1
<3> 72 Yes INFO: task hung in vfs_unlink (5)
https://syzkaller.appspot.com/bug?extid=6983c03a6a28616e362f
<4> 59 No KCSAN: data-race in fat12_ent_put / fat_mirror_bhs
https://syzkaller.appspot.com/bug?extid=51b4c65bb770155d058f
<5> 26 Yes WARNING in fanotify_handle_event (2)
https://syzkaller.appspot.com/bug?extid=318aab2cf26bb7d40228
<6> 12 Yes WARNING in filename_symlinkat
https://syzkaller.appspot.com/bug?extid=2ed46b6b748df855347f
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
To disable reminders for individual bugs, reply with the following command:
#syz set <Ref> no-reminders
To change bug's subsystems, reply with:
#syz set <Ref> subsystems: new-subsystem
You may send multiple commands in a single email message.
reply other threads:[~2026-04-15 12:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=69df86fe.a70a0220.7fc2.0000.GAE@google.com \
--to=syzbot+list913c0c36c9616478c625@syzkaller.appspotmail.com \
--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 \
/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