From: syzbot <syzbot+10e8dae9863cb83db623@syzkaller.appspotmail.com>
To: clm@fb.com, dsterba@suse.com, josef@toxicpanda.com,
linux-btrfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, nborisov@suse.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [btrfs?] WARNING in btrfs_release_global_block_rsv
Date: Sun, 19 Nov 2023 16:46:07 -0800 [thread overview]
Message-ID: <000000000000c206db060a8acf37@google.com> (raw)
In-Reply-To: <000000000000cf826706067d18fd@google.com>
syzbot has bisected this issue to:
commit c18e3235646a8ba74d013067a6475c8d262d3776
Author: Josef Bacik <josef@toxicpanda.com>
Date: Thu Dec 2 20:34:32 2021 +0000
btrfs: reserve extra space for the free space tree
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10528fb7680000
start commit: 23dfa043f6d5 Merge tag 'i2c-for-6.7-rc2' of git://git.kern..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=12528fb7680000
console output: https://syzkaller.appspot.com/x/log.txt?x=14528fb7680000
kernel config: https://syzkaller.appspot.com/x/.config?x=d05dd66e2eb2c872
dashboard link: https://syzkaller.appspot.com/bug?extid=10e8dae9863cb83db623
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17722e24e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11201350e80000
Reported-by: syzbot+10e8dae9863cb83db623@syzkaller.appspotmail.com
Fixes: c18e3235646a ("btrfs: reserve extra space for the free space tree")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-11-20 0:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 10:43 [syzbot] [btrfs?] WARNING in btrfs_release_global_block_rsv syzbot
2023-11-19 6:06 ` syzbot
2023-11-20 0:46 ` syzbot [this message]
2024-02-24 9:37 ` 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=000000000000c206db060a8acf37@google.com \
--to=syzbot+10e8dae9863cb83db623@syzkaller.appspotmail.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nborisov@suse.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;
as well as URLs for NNTP newsgroup(s).