From: syzbot <syzbot+list4af3b8ed9549444d90bf@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 (Dec 2024)
Date: Sat, 07 Dec 2024 08:12:26 -0800 [thread overview]
Message-ID: <675473ea.050a0220.a30f1.0159.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, 3 new issues were detected and 1 were fixed.
In total, 12 issues are still open and 19 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 3225 Yes INFO: task hung in exfat_write_inode
https://syzkaller.appspot.com/bug?extid=2f73ed585f115e98aee8
<2> 1854 No INFO: task hung in exfat_sync_fs
https://syzkaller.appspot.com/bug?extid=205c2644abdff9d3f9fc
<3> 394 Yes WARNING in __brelse (3)
https://syzkaller.appspot.com/bug?extid=ce3af36144a13b018cc7
<4> 36 Yes KMSAN: uninit-value in iov_iter_alignment_iovec
https://syzkaller.appspot.com/bug?extid=f2a9c06bfaa027217ebb
<5> 8 Yes KMSAN: kernel-infoleak in pipe_read
https://syzkaller.appspot.com/bug?extid=41ebd857f013384237a9
<6> 2 No possible deadlock in __generic_file_fsync (2)
https://syzkaller.appspot.com/bug?extid=625941ecc67c107ef2bd
---
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:[~2024-12-07 16:12 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=675473ea.050a0220.a30f1.0159.GAE@google.com \
--to=syzbot+list4af3b8ed9549444d90bf@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 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.