From: syzbot <syzbot+list097cc95b0664fec261ec@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 (Jan 2025)
Date: Tue, 07 Jan 2025 06:54:26 -0800 [thread overview]
Message-ID: <677d4022.050a0220.a40f5.0020.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, 1 new issues were detected and 1 were fixed.
In total, 14 issues are still open and 21 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 3312 Yes INFO: task hung in exfat_write_inode
https://syzkaller.appspot.com/bug?extid=2f73ed585f115e98aee8
<2> 1094 Yes WARNING in __brelse (3)
https://syzkaller.appspot.com/bug?extid=ce3af36144a13b018cc7
<3> 60 Yes KMSAN: uninit-value in iov_iter_alignment_iovec
https://syzkaller.appspot.com/bug?extid=f2a9c06bfaa027217ebb
<4> 16 No general protection fault in exfat_init_dir_entry
https://syzkaller.appspot.com/bug?extid=ff3c3b48f27747505446
<5> 14 Yes general protection fault in exfat_get_dentry_cached
https://syzkaller.appspot.com/bug?extid=8f8fe64a30c50b289a18
<6> 12 Yes KMSAN: kernel-infoleak in pipe_read
https://syzkaller.appspot.com/bug?extid=41ebd857f013384237a9
<7> 11 Yes INFO: task hung in chmod_common (5)
https://syzkaller.appspot.com/bug?extid=4426dfa686191fab8b50
<8> 7 Yes INFO: task hung in exfat_lookup (3)
https://syzkaller.appspot.com/bug?extid=73c8cd74d6440aef4d6a
<9> 6 Yes general protection fault in exfat_find_empty_entry
https://syzkaller.appspot.com/bug?extid=8941485e471cec199c9e
---
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:[~2025-01-07 14:54 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=677d4022.050a0220.a40f5.0020.GAE@google.com \
--to=syzbot+list097cc95b0664fec261ec@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