From: syzbot <syzbot+list0253d0b13abd2f4c7f49@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
Date: Mon, 27 Mar 2023 04:07:45 -0700 [thread overview]
Message-ID: <000000000000a739a605f7dfc08d@google.com> (raw)
Hello jfs maintainers/developers,
This is a 30-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, 3 new issues were detected and 0 were fixed.
In total, 69 issues are still open and 7 have been fixed so far.
Some of the still happening issues:
Crashes Repro Title
3712 Yes UBSAN: shift-out-of-bounds in extAlloc
https://syzkaller.appspot.com/bug?extid=5f088f29593e6b4c8db8
828 Yes UBSAN: array-index-out-of-bounds in xtInsert
https://syzkaller.appspot.com/bug?extid=55a7541cfd25df68109e
483 Yes general protection fault in lmLogSync (2)
https://syzkaller.appspot.com/bug?extid=e14b1036481911ae4d77
326 Yes kernel BUG in jfs_evict_inode
https://syzkaller.appspot.com/bug?extid=9c0c58ea2e4887ab502e
282 Yes general protection fault in write_special_inodes
https://syzkaller.appspot.com/bug?extid=c732e285f8fc38d15916
184 Yes kernel BUG in txUnlock
https://syzkaller.appspot.com/bug?extid=a63afa301d1258d09267
143 Yes UBSAN: array-index-out-of-bounds in txCommit
https://syzkaller.appspot.com/bug?extid=0558d19c373e44da3c18
102 Yes general protection fault in jfs_flush_journal
https://syzkaller.appspot.com/bug?extid=194bfe3476f96782c0b6
74 Yes kernel BUG in dbFindLeaf
https://syzkaller.appspot.com/bug?extid=dcea2548c903300a400e
51 Yes KASAN: use-after-free Read in diFree
https://syzkaller.appspot.com/bug?extid=1964c915c8c3913b3d7a
---
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.
reply other threads:[~2023-03-27 11:08 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=000000000000a739a605f7dfc08d@google.com \
--to=syzbot+list0253d0b13abd2f4c7f49@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