From: syzbot <syzbot+cb79de2cc8b76fbf474f@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tao1.yu@intel.com
Subject: Re: [syzbot] [gfs2?] general protection fault in _find_first_zero_bit
Date: Mon, 03 Aug 2026 02:16:02 -0700 [thread overview]
Message-ID: <6a705c52.f794c993.27aeb.0029.GAE@google.com> (raw)
In-Reply-To: <7c9b7148-7f92-4e22-8818-41abc87145ecn@googlegroups.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+cb79de2cc8b76fbf474f@syzkaller.appspotmail.com
Tested-by: syzbot+cb79de2cc8b76fbf474f@syzkaller.appspotmail.com
Tested on:
commit: b7d16f69 gfs2: mark the VFS superblock read-only befor..
git tree: https://github.com/yutao-intel/linux.git fix-gfs2
console output: https://syzkaller.appspot.com/x/log.txt?x=151bbdb9580000
kernel config: https://syzkaller.appspot.com/x/.config?x=86ba763b42fa66a
dashboard link: https://syzkaller.appspot.com/bug?extid=cb79de2cc8b76fbf474f
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2026-08-03 9:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7c9b7148-7f92-4e22-8818-41abc87145ecn@googlegroups.com>
2026-08-03 9:16 ` syzbot [this message]
[not found] <e9ec9dca-e808-48b9-90fc-af7745a4c178n@googlegroups.com>
2026-08-03 7:14 ` [syzbot] [gfs2?] general protection fault in _find_first_zero_bit syzbot
[not found] <20260630000607.92380-1-kartikey406@gmail.com>
2026-06-30 3:06 ` syzbot
2026-06-29 20:48 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=6a705c52.f794c993.27aeb.0029.GAE@google.com \
--to=syzbot+cb79de2cc8b76fbf474f@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tao1.yu@intel.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