From: syzbot <syzbot+list419fa0b9f3f2be463473@syzkaller.appspotmail.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [syzbot] Monthly gfs2 report (May 2023)
Date: Wed, 31 May 2023 01:44:18 -0700 [thread overview]
Message-ID: <00000000000051530605fcf95365@google.com> (raw)
Hello gfs2 maintainers/developers,
This is a 31-day syzbot report for the gfs2 subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/gfs2
During the period, 1 new issues were detected and 0 were fixed.
In total, 19 issues are still open and 17 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 1592 Yes WARNING in __folio_mark_dirty (2)
https://syzkaller.appspot.com/bug?extid=e14d6cd6ec241f507ba7
<2> 437 Yes kernel BUG in gfs2_glock_nq (2)
https://syzkaller.appspot.com/bug?extid=70f4e455dee59ab40c80
<3> 51 Yes INFO: task hung in gfs2_gl_hash_clear (3)
https://syzkaller.appspot.com/bug?extid=ed7d0f71a89e28557a77
<4> 34 Yes WARNING in gfs2_check_blk_type
https://syzkaller.appspot.com/bug?extid=092b28923eb79e0f3c41
<5> 32 Yes general protection fault in gfs2_dump_glock (2)
https://syzkaller.appspot.com/bug?extid=427fed3295e9a7e887f2
<6> 23 Yes INFO: task hung in __gfs2_trans_begin
https://syzkaller.appspot.com/bug?extid=a159cc6676345e04ff7d
<7> 5 Yes BUG: sleeping function called from invalid context in gfs2_glock_wait
https://syzkaller.appspot.com/bug?extid=cdb448c6e82c20d7960c
---
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.
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:[~2023-05-31 8:44 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=00000000000051530605fcf95365@google.com \
--to=syzbot+list419fa0b9f3f2be463473@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).