From: syzbot <syzbot+5fd11a1f057a67a03a1b@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,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [btrfs?] WARNING in btrfs_create_pending_block_groups
Date: Tue, 13 Feb 2024 05:22:02 -0800 [thread overview]
Message-ID: <000000000000a545940611434746@google.com> (raw)
In-Reply-To: <0000000000000faabc05ee84f596@google.com>
syzbot suspects this issue was fixed by commit:
commit a1912f712188291f9d7d434fba155461f1ebef66
Author: Josef Bacik <josef@toxicpanda.com>
Date: Wed Nov 22 17:17:55 2023 +0000
btrfs: remove code for inode_cache and recovery mount options
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=113ba042180000
start commit: a4d7d7011219 Merge tag 'spi-fix-v6.4-rc5' of git://git.ker..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=7474de833c217bf4
dashboard link: https://syzkaller.appspot.com/bug?extid=5fd11a1f057a67a03a1b
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17887659280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13ac4e93280000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: btrfs: remove code for inode_cache and recovery mount options
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next parent reply other threads:[~2024-02-13 13:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0000000000000faabc05ee84f596@google.com>
2024-02-13 13:22 ` syzbot [this message]
2024-02-13 18:01 ` [syzbot] [btrfs?] WARNING in btrfs_create_pending_block_groups David Sterba
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=000000000000a545940611434746@google.com \
--to=syzbot+5fd11a1f057a67a03a1b@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=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).