From: syzbot <syzbot+list47b21a48b702e3bbf3ac@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 (Oct 2024)
Date: Mon, 14 Oct 2024 12:37:27 -0700 [thread overview]
Message-ID: <670d72f7.050a0220.3e960.00db.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, 5 new issues were detected and 0 were fixed.
In total, 53 issues are still open and 47 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 21984 Yes kernel BUG in jfs_evict_inode
https://syzkaller.appspot.com/bug?extid=9c0c58ea2e4887ab502e
<2> 9592 Yes kernel BUG in txUnlock
https://syzkaller.appspot.com/bug?extid=a63afa301d1258d09267
<3> 4135 Yes general protection fault in lmLogSync (2)
https://syzkaller.appspot.com/bug?extid=e14b1036481911ae4d77
<4> 3333 Yes WARNING in dbAdjTree
https://syzkaller.appspot.com/bug?extid=ab18fa9c959320611727
<5> 2354 Yes INFO: task hung in lock_metapage
https://syzkaller.appspot.com/bug?extid=1d84a1682e4673d5c4fb
<6> 2169 Yes general protection fault in write_special_inodes
https://syzkaller.appspot.com/bug?extid=c732e285f8fc38d15916
<7> 2031 Yes kernel BUG in dbFindLeaf
https://syzkaller.appspot.com/bug?extid=dcea2548c903300a400e
<8> 1946 Yes KASAN: user-memory-access Write in __destroy_inode
https://syzkaller.appspot.com/bug?extid=dcc068159182a4c31ca3
<9> 1021 Yes KASAN: use-after-free Read in release_metapage
https://syzkaller.appspot.com/bug?extid=f1521383cec5f7baaa94
<10> 907 Yes general protection fault in jfs_flush_journal
https://syzkaller.appspot.com/bug?extid=194bfe3476f96782c0b6
---
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-10-14 19:37 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=670d72f7.050a0220.3e960.00db.GAE@google.com \
--to=syzbot+list47b21a48b702e3bbf3ac@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.