From: syzbot <syzbot+listb51f932ee38ecac1b05d@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 (Nov 2023)
Date: Mon, 27 Nov 2023 13:03:34 -0800 [thread overview]
Message-ID: <0000000000009401fb060b28a2e1@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 0 were fixed.
In total, 7 issues are still open and 12 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 225 No INFO: task hung in path_openat (7)
https://syzkaller.appspot.com/bug?extid=950a0cdaa2fdd14f5bdc
<2> 150 No INFO: task hung in exfat_sync_fs
https://syzkaller.appspot.com/bug?extid=205c2644abdff9d3f9fc
<3> 119 Yes WARNING in drop_nlink (2)
https://syzkaller.appspot.com/bug?extid=651ca866e5e2b4b5095b
<4> 38 Yes INFO: task hung in exfat_write_inode
https://syzkaller.appspot.com/bug?extid=2f73ed585f115e98aee8
<5> 1 No UBSAN: shift-out-of-bounds in exfat_fill_super (2)
https://syzkaller.appspot.com/bug?extid=d33808a177641a02213e
---
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.
next reply other threads:[~2023-11-27 21:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 21:03 syzbot [this message]
2023-11-29 14:09 ` [syzbot] Monthly exfat report (Nov 2023) Namjae Jeon
2023-11-29 15:48 ` Aleksandr Nogikh
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=0000000000009401fb060b28a2e1@google.com \
--to=syzbot+listb51f932ee38ecac1b05d@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;
as well as URLs for NNTP newsgroup(s).