From: syzbot <syzbot+listb58444abba4ac0e01683@syzkaller.appspotmail.com>
To: gfs2@lists.linux.dev, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly gfs2 report (Jan 2025)
Date: Mon, 06 Jan 2025 02:01:26 -0800 [thread overview]
Message-ID: <677ba9f6.050a0220.a40f5.0004.GAE@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, 15 issues are still open and 34 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 635844 Yes WARNING in __folio_mark_dirty (2)
https://syzkaller.appspot.com/bug?extid=e14d6cd6ec241f507ba7
<2> 1342 Yes kernel BUG in gfs2_glock_nq (2)
https://syzkaller.appspot.com/bug?extid=70f4e455dee59ab40c80
<3> 928 Yes kernel BUG in gfs2_withdraw
https://syzkaller.appspot.com/bug?extid=ed42f17ebcb58526788c
<4> 337 Yes KASAN: stack-out-of-bounds Read in gfs2_dump_glock
https://syzkaller.appspot.com/bug?extid=7efd59a5a532c57037e6
<5> 133 Yes INFO: task hung in __gfs2_lookup
https://syzkaller.appspot.com/bug?extid=8a86bdd8c524e46ff97a
<6> 30 Yes WARNING in gfs2_ri_update (2)
https://syzkaller.appspot.com/bug?extid=7567dc5c8aa8f68bde74
<7> 29 Yes INFO: task hung in gfs2_glock_nq
https://syzkaller.appspot.com/bug?extid=dbb72d38131e90dc1f66
<8> 17 Yes WARNING in gfs2_check_blk_type (2)
https://syzkaller.appspot.com/bug?extid=26e96d7e92eed8a21405
<9> 7 Yes kernel BUG in gfs2_assert_warn_i
https://syzkaller.appspot.com/bug?extid=ffe01cefd437cbde362b
<10> 7 Yes KASAN: slab-use-after-free Read in gfs2_invalidate_folio
https://syzkaller.appspot.com/bug?extid=3a36aeabd31497d63f6e
---
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:[~2025-01-06 10:01 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=677ba9f6.050a0220.a40f5.0004.GAE@google.com \
--to=syzbot+listb58444abba4ac0e01683@syzkaller.appspotmail.com \
--cc=gfs2@lists.linux.dev \
--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