From: syzbot <syzbot+9295d5153c44d86af0aa@syzkaller.appspotmail.com>
To: clm@fb.com, dsterba@suse.com, josef@toxicpanda.com,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
loemra.dev@gmail.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [btrfs?] kernel BUG in extent_writepage_io
Date: Sun, 26 Oct 2025 05:34:03 -0700 [thread overview]
Message-ID: <68fe153b.050a0220.3344a1.0090.GAE@google.com> (raw)
In-Reply-To: <6716f9e2.050a0220.1e4b4d.0068.GAE@google.com>
syzbot suspects this issue was fixed by commit:
commit cba7c35fec267188a9708deae857e9116c57497b
Author: Leo Martins <loemra.dev@gmail.com>
Date: Tue Aug 12 23:28:27 2025 +0000
btrfs: move ref-verify under CONFIG_BTRFS_DEBUG
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13ea5614580000
start commit: 6efbea77b390 Merge tag 'arm64-fixes' of git://git.kernel.o..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=164d2822debd8b0d
dashboard link: https://syzkaller.appspot.com/bug?extid=9295d5153c44d86af0aa
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15c18c5f980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12186f27980000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: btrfs: move ref-verify under CONFIG_BTRFS_DEBUG
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-10-26 12:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 1:03 [syzbot] [btrfs?] kernel BUG in extent_writepage_io syzbot
2025-10-26 12:34 ` syzbot [this message]
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=68fe153b.050a0220.3344a1.0090.GAE@google.com \
--to=syzbot+9295d5153c44d86af0aa@syzkaller.appspotmail.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loemra.dev@gmail.com \
--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