From: syzbot <syzbot+48ed002119c0f19daf63@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?] WARNING in btrfs_release_global_block_rsv (2)
Date: Wed, 15 Oct 2025 09:18:03 -0700 [thread overview]
Message-ID: <68efc93b.050a0220.91a22.02a3.GAE@google.com> (raw)
In-Reply-To: <673d458f.050a0220.363a1b.0003.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=1176267c580000
start commit: f868cd251776 Merge tag 'drm-fixes-2024-11-16' of https://g..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=1503500c6f615d24
dashboard link: https://syzkaller.appspot.com/bug?extid=48ed002119c0f19daf63
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11dfd130580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15dfd130580000
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-15 16:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 2:12 [syzbot] [btrfs?] WARNING in btrfs_release_global_block_rsv (2) syzbot
2025-10-15 16:18 ` 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=68efc93b.050a0220.91a22.02a3.GAE@google.com \
--to=syzbot+48ed002119c0f19daf63@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.