From: syzbot <syzbot+list87c7a7f61f75d325f246@syzkaller.appspotmail.com>
To: dwmw2@infradead.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
richard@nod.at, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly jffs2 report (Apr 2024)
Date: Sat, 13 Apr 2024 03:29:23 -0700 [thread overview]
Message-ID: <000000000000b005380615f7dc07@google.com> (raw)
Hello jffs2 maintainers/developers,
This is a 31-day syzbot report for the jffs2 subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/jffs2
During the period, 9 new issues were detected and 0 were fixed.
In total, 9 issues are still open and 1 has been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 616 Yes kernel BUG in jffs2_del_ino_cache
https://syzkaller.appspot.com/bug?extid=44664704c1494ad5f7a0
<2> 12 Yes KASAN: slab-use-after-free Read in jffs2_garbage_collect_pass
https://syzkaller.appspot.com/bug?extid=e84662c5f30b8c401437
<3> 7 Yes KASAN: slab-out-of-bounds Read in jffs2_sum_add_kvec
https://syzkaller.appspot.com/bug?extid=d7c218ea1def103f6bcd
---
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.
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
reply other threads:[~2024-04-13 10:29 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=000000000000b005380615f7dc07@google.com \
--to=syzbot+list87c7a7f61f75d325f246@syzkaller.appspotmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).