From: syzbot <syzbot+list421f13bcf36317d2fd2e@syzkaller.appspotmail.com>
To: jfs-discussion@lists.sourceforge.net,
linux-kernel@vger.kernel.org, shaggy@kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly jfs report (Nov 2026)
Date: Mon, 02 Nov 2026 20:33:58 -0800 [thread overview]
Message-ID: <6ae96436.abb90550.19e2c9.0000.GAE@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, 0 new issues were detected and 0 were fixed.
In total, 64 issues are still open and 73 have already been fixed.
There is also 1 low-priority issue.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 110743 Yes kernel BUG in jfs_evict_inode
https://syzkaller.appspot.com/bug?extid=9c0c58ea2e4887ab502e
<2> 96427 Yes KASAN: slab-use-after-free Read in lbmIODone
https://syzkaller.appspot.com/bug?extid=ecf51a7ccb6b1394e90c
<3> 55459 Yes WARNING in dbAdjTree
https://syzkaller.appspot.com/bug?extid=ab18fa9c959320611727
<4> 50442 Yes kernel BUG in txUnlock
https://syzkaller.appspot.com/bug?extid=a63afa301d1258d09267
<5> 9261 Yes general protection fault in txEnd
https://syzkaller.appspot.com/bug?extid=1d096d31de6a0491b55e
<6> 8201 Yes KASAN: slab-use-after-free Write in dtSplitPage
https://syzkaller.appspot.com/bug?extid=a939a1121380d3212940
<7> 8178 Yes kernel BUG in dbFindLeaf
https://syzkaller.appspot.com/bug?extid=dcea2548c903300a400e
<8> 5481 Yes INFO: task hung in lock_metapage
https://syzkaller.appspot.com/bug?extid=1d84a1682e4673d5c4fb
<9> 3323 Yes UBSAN: array-index-out-of-bounds in dtInsertEntry
https://syzkaller.appspot.com/bug?extid=5f7f0caf9979e9d09ff8
<10> 2762 Yes WARNING in dbJoin
https://syzkaller.appspot.com/bug?extid=a67911c5a11315aa55a8
---
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:[~2026-11-03 4:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 4:33 syzbot [this message]
2026-11-10 10:48 ` [PATCH] jfs: add dmap integrity check to prevent out-of-bounds tree access Shuai Liu
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=6ae96436.abb90550.19e2c9.0000.GAE@google.com \
--to=syzbot+list421f13bcf36317d2fd2e@syzkaller.appspotmail.com \
--cc=jfs-discussion@lists.sourceforge.net \
--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 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.