From: syzbot <syzbot+listb3db0d154d5465951dfe@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 (Feb 2026)
Date: Thu, 26 Feb 2026 04:58:35 -0800 [thread overview]
Message-ID: <69a0437b.a00a0220.21906d.00e7.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, 72 issues are still open and 66 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 92526 Yes kernel BUG in jfs_evict_inode
https://syzkaller.appspot.com/bug?extid=9c0c58ea2e4887ab502e
<2> 48984 Yes WARNING in dbAdjTree
https://syzkaller.appspot.com/bug?extid=ab18fa9c959320611727
<3> 41630 Yes kernel BUG in txUnlock
https://syzkaller.appspot.com/bug?extid=a63afa301d1258d09267
<4> 8098 Yes general protection fault in lmLogSync (2)
https://syzkaller.appspot.com/bug?extid=e14b1036481911ae4d77
<5> 6968 Yes KASAN: slab-use-after-free Write in dtSplitPage
https://syzkaller.appspot.com/bug?extid=a939a1121380d3212940
<6> 6578 Yes kernel BUG in dbFindLeaf
https://syzkaller.appspot.com/bug?extid=dcea2548c903300a400e
<7> 5114 Yes general protection fault in txEnd
https://syzkaller.appspot.com/bug?extid=1d096d31de6a0491b55e
<8> 4816 Yes INFO: task hung in lock_metapage
https://syzkaller.appspot.com/bug?extid=1d84a1682e4673d5c4fb
<9> 4364 Yes general protection fault in jfs_flush_journal
https://syzkaller.appspot.com/bug?extid=194bfe3476f96782c0b6
<10> 3550 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:[~2026-02-26 12:58 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=69a0437b.a00a0220.21906d.00e7.GAE@google.com \
--to=syzbot+listb3db0d154d5465951dfe@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox