From: syzbot <syzbot+10e8dae9863cb83db623@syzkaller.appspotmail.com>
To: anand.jain@oracle.com, brauner@kernel.org, clm@fb.com,
dsterba@suse.com, johannes.thumshirn@wdc.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: Sat, 24 Feb 2024 01:37:02 -0800 [thread overview]
Message-ID: <0000000000003d0afb06121d6b34@google.com> (raw)
In-Reply-To: <000000000000cf826706067d18fd@google.com>
syzbot suspects this issue was fixed by commit:
commit a6a8f22a4af6c572d9e01ca9f7b515bf0cbb63b1
Author: Josef Bacik <josef@toxicpanda.com>
Date: Wed Nov 22 17:17:40 2023 +0000
btrfs: move space cache settings into open_ctree
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=100fec54180000
start commit: 23dfa043f6d5 Merge tag 'i2c-for-6.7-rc2' of git://git.kern..
git tree: upstream
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
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: btrfs: move space cache settings into open_ctree
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-02-24 9:37 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
2024-02-24 9:37 ` 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=0000000000003d0afb06121d6b34@google.com \
--to=syzbot+10e8dae9863cb83db623@syzkaller.appspotmail.com \
--cc=anand.jain@oracle.com \
--cc=brauner@kernel.org \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=johannes.thumshirn@wdc.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).