From: syzbot <syzbot+list255c96014713c46a953c@syzkaller.appspotmail.com>
To: gfs2@lists.linux.dev, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly gfs2 report (Nov 2023)
Date: Mon, 06 Nov 2023 15:07:27 -0800 [thread overview]
Message-ID: <000000000000ef8d3b060983eae7@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, 0 new issues were detected and 0 were fixed.
In total, 21 issues are still open and 22 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 4449 Yes WARNING in __folio_mark_dirty (2)
https://syzkaller.appspot.com/bug?extid=e14d6cd6ec241f507ba7
<2> 3678 Yes WARNING in folio_account_dirtied
https://syzkaller.appspot.com/bug?extid=8d1d62bfb63d6a480be1
<3> 662 Yes kernel BUG in gfs2_glock_nq (2)
https://syzkaller.appspot.com/bug?extid=70f4e455dee59ab40c80
<4> 79 Yes INFO: task hung in gfs2_gl_hash_clear (3)
https://syzkaller.appspot.com/bug?extid=ed7d0f71a89e28557a77
<5> 54 Yes WARNING in gfs2_check_blk_type
https://syzkaller.appspot.com/bug?extid=092b28923eb79e0f3c41
<6> 35 Yes general protection fault in gfs2_dump_glock (2)
https://syzkaller.appspot.com/bug?extid=427fed3295e9a7e887f2
<7> 9 Yes BUG: unable to handle kernel NULL pointer dereference in gfs2_rgrp_dump
https://syzkaller.appspot.com/bug?extid=da0fc229cc1ff4bb2e6d
<8> 4 Yes BUG: unable to handle kernel NULL pointer dereference in gfs2_rindex_update
https://syzkaller.appspot.com/bug?extid=2b32df23ff6b5b307565
---
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:[~2023-11-06 23:07 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=000000000000ef8d3b060983eae7@google.com \
--to=syzbot+list255c96014713c46a953c@syzkaller.appspotmail.com \
--cc=gfs2@lists.linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).