From: syzbot <syzbot+list5219cabcace6cc8e0864@syzkaller.appspotmail.com>
To: jfs-discussion@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
shaggy@kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly jfs report (Apr 2024)
Date: Mon, 08 Apr 2024 01:30:27 -0700 [thread overview]
Message-ID: <000000000000198fc20615919e19@google.com> (raw)
Hello jfs maintainers/developers,
This is a 31-day syzbot report for the jfs subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/jfs
During the period, 4 new issues were detected and 0 were fixed.
In total, 26 issues are still open and 39 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 1934 Yes general protection fault in lmLogSync (2)
https://syzkaller.appspot.com/bug?extid=e14b1036481911ae4d77
<2> 1762 Yes kernel BUG in jfs_evict_inode
https://syzkaller.appspot.com/bug?extid=9c0c58ea2e4887ab502e
<3> 1098 Yes general protection fault in write_special_inodes
https://syzkaller.appspot.com/bug?extid=c732e285f8fc38d15916
<4> 598 Yes kernel BUG in txUnlock
https://syzkaller.appspot.com/bug?extid=a63afa301d1258d09267
<5> 583 Yes WARNING in inc_nlink (3)
https://syzkaller.appspot.com/bug?extid=2b3af42c0644df1e4da9
<6> 412 Yes general protection fault in jfs_flush_journal
https://syzkaller.appspot.com/bug?extid=194bfe3476f96782c0b6
<7> 233 Yes kernel BUG in dbFindLeaf
https://syzkaller.appspot.com/bug?extid=dcea2548c903300a400e
<8> 92 Yes kernel BUG in lbmIODone
https://syzkaller.appspot.com/bug?extid=52ddb6c83a04ca55f975
<9> 82 Yes KASAN: use-after-free Read in lbmIODone (2)
https://syzkaller.appspot.com/bug?extid=aca408372ef0b470a3d2
<10> 74 Yes KASAN: use-after-free Read in jfs_lazycommit
https://syzkaller.appspot.com/bug?extid=885a4f3281b8d99c48d8
---
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-04-08 8:30 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=000000000000198fc20615919e19@google.com \
--to=syzbot+list5219cabcace6cc8e0864@syzkaller.appspotmail.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaggy@kernel.org \
--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).