From: syzbot <syzbot+3e2c95229d1ab81a0bfd@syzkaller.appspotmail.com>
To: anprice@redhat.com, gfs2@lists.linux.dev,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [gfs2?] WARNING in rgblk_free (2)
Date: Mon, 12 Jan 2026 11:34:02 -0800 [thread overview]
Message-ID: <69654caa.050a0220.38aacd.0000.GAE@google.com> (raw)
In-Reply-To: <bfe98f76-2c8a-4bb9-a37a-f9b184a9621f@redhat.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+3e2c95229d1ab81a0bfd@syzkaller.appspotmail.com
Tested-by: syzbot+3e2c95229d1ab81a0bfd@syzkaller.appspotmail.com
Tested on:
commit: 0f61b186 Linux 6.19-rc5
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1030a99a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=3027d9a5f96d82ca
dashboard link: https://syzkaller.appspot.com/bug?extid=3e2c95229d1ab81a0bfd
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=13a3e5fa580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2026-01-12 19:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 15:49 [syzbot] [gfs2?] WARNING in rgblk_free (2) syzbot
2026-01-12 19:12 ` Andrew Price
2026-01-12 19:34 ` syzbot [this message]
2026-04-17 10:12 ` Forwarded: [PATCH] gfs2: replace WARN_ON_ONCE with error message in syzbot
2026-04-17 16:21 ` Forwarded: Re: [syzbot] WARNING in rgblk_free syzbot
[not found] <20260417101233.2491241-1-tristmd@gmail.com>
2026-04-17 10:28 ` [syzbot] [gfs2?] WARNING in rgblk_free (2) syzbot
[not found] <177644289258.3790799.12048821960579541469@talencesecurity.com>
2026-04-17 16:38 ` syzbot
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=69654caa.050a0220.38aacd.0000.GAE@google.com \
--to=syzbot+3e2c95229d1ab81a0bfd@syzkaller.appspotmail.com \
--cc=anprice@redhat.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