From: syzbot <syzbot+dde7e853812ed57835ea@syzkaller.appspotmail.com>
To: 18801353760@163.com, 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,
llvm@lists.linux.dev, nathan@kernel.org,
ndesaulniers@google.com, syzkaller-bugs@googlegroups.com,
trix@redhat.com, yin31149@gmail.com
Subject: Re: [syzbot] [btrfs?] WARNING in btrfs_block_rsv_release
Date: Fri, 02 Feb 2024 18:07:04 -0800 [thread overview]
Message-ID: <00000000000052fe42061070afc4@google.com> (raw)
In-Reply-To: <0000000000002a909705eb841dda@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=149a0a38180000
start commit: 7287904c8771 Merge tag 'for-linus-2023011801' of git://git..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=d24faf5fc10540ae
dashboard link: https://syzkaller.appspot.com/bug?extid=dde7e853812ed57835ea
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14f7a805480000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10df5afe480000
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
prev parent reply other threads:[~2024-02-03 2:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 4:45 [syzbot] WARNING in btrfs_block_rsv_release syzbot
2022-10-28 11:13 ` Hawkins Jiawei
2022-10-28 14:02 ` syzbot
2022-10-28 15:05 ` Hawkins Jiawei
2022-10-28 15:29 ` syzbot
2022-10-28 15:32 ` Hawkins Jiawei
2022-10-28 16:25 ` syzbot
2024-02-03 2:07 ` 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=00000000000052fe42061070afc4@google.com \
--to=syzbot+dde7e853812ed57835ea@syzkaller.appspotmail.com \
--cc=18801353760@163.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=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=trix@redhat.com \
--cc=yin31149@gmail.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).