From: syzbot <syzbot+list6e220af77940a0f2148c@syzkaller.appspotmail.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [syzbot] Monthly cluster report
Date: Tue, 28 Mar 2023 09:19:02 -0700 [thread overview]
Message-ID: <000000000000bdc7df05f7f837ff@google.com> (raw)
Hello cluster maintainers/developers,
This is a 30-day syzbot report for the cluster subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/cluster
During the period, 1 new issues were detected and 0 were fixed.
In total, 23 issues are still open and 12 have been fixed so far.
Some of the still happening issues:
Crashes Repro Title
237 Yes kernel BUG in gfs2_glock_nq (2)
https://syzkaller.appspot.com/bug?extid=70f4e455dee59ab40c80
111 Yes INFO: task hung in gfs2_jhead_process_page
https://syzkaller.appspot.com/bug?extid=b9c5afe053a08cd29468
108 Yes general protection fault in gfs2_evict_inode (2)
https://syzkaller.appspot.com/bug?extid=8a5fc6416c175cecea34
23 Yes INFO: task hung in __gfs2_trans_begin
https://syzkaller.appspot.com/bug?extid=a159cc6676345e04ff7d
21 Yes WARNING in gfs2_check_blk_type
https://syzkaller.appspot.com/bug?extid=092b28923eb79e0f3c41
18 Yes UBSAN: array-index-out-of-bounds in __gfs2_iomap_get
https://syzkaller.appspot.com/bug?extid=45d4691b1ed3c48eba05
13 Yes INFO: task hung in gfs2_gl_hash_clear (3)
https://syzkaller.appspot.com/bug?extid=ed7d0f71a89e28557a77
6 No KMSAN: uninit-value in inode_go_dump
https://syzkaller.appspot.com/bug?extid=79333ce1ae874ab7ffbb
3 Yes general protection fault in gfs2_dump_glock (2)
https://syzkaller.appspot.com/bug?extid=427fed3295e9a7e887f2
---
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 at googlegroups.com.
WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+list6e220af77940a0f2148c@syzkaller.appspotmail.com>
To: cluster-devel@redhat.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly cluster report
Date: Tue, 28 Mar 2023 09:19:02 -0700 [thread overview]
Message-ID: <000000000000bdc7df05f7f837ff@google.com> (raw)
Hello cluster maintainers/developers,
This is a 30-day syzbot report for the cluster subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/cluster
During the period, 1 new issues were detected and 0 were fixed.
In total, 23 issues are still open and 12 have been fixed so far.
Some of the still happening issues:
Crashes Repro Title
237 Yes kernel BUG in gfs2_glock_nq (2)
https://syzkaller.appspot.com/bug?extid=70f4e455dee59ab40c80
111 Yes INFO: task hung in gfs2_jhead_process_page
https://syzkaller.appspot.com/bug?extid=b9c5afe053a08cd29468
108 Yes general protection fault in gfs2_evict_inode (2)
https://syzkaller.appspot.com/bug?extid=8a5fc6416c175cecea34
23 Yes INFO: task hung in __gfs2_trans_begin
https://syzkaller.appspot.com/bug?extid=a159cc6676345e04ff7d
21 Yes WARNING in gfs2_check_blk_type
https://syzkaller.appspot.com/bug?extid=092b28923eb79e0f3c41
18 Yes UBSAN: array-index-out-of-bounds in __gfs2_iomap_get
https://syzkaller.appspot.com/bug?extid=45d4691b1ed3c48eba05
13 Yes INFO: task hung in gfs2_gl_hash_clear (3)
https://syzkaller.appspot.com/bug?extid=ed7d0f71a89e28557a77
6 No KMSAN: uninit-value in inode_go_dump
https://syzkaller.appspot.com/bug?extid=79333ce1ae874ab7ffbb
3 Yes general protection fault in gfs2_dump_glock (2)
https://syzkaller.appspot.com/bug?extid=427fed3295e9a7e887f2
---
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.
next reply other threads:[~2023-03-28 16:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 16:19 syzbot [this message]
2023-03-28 16:19 ` [syzbot] Monthly cluster report syzbot
2023-03-30 10:09 ` [Cluster-devel] " Aleksandr Nogikh
2023-03-30 10:09 ` Aleksandr Nogikh
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=000000000000bdc7df05f7f837ff@google.com \
--to=syzbot+list6e220af77940a0f2148c@syzkaller.appspotmail.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.