From: syzbot <syzbot+10d5b62a8d7046b86d22@syzkaller.appspotmail.com>
To: anand.jain@oracle.com, clm@fb.com, dsterba@suse.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_use_block_rsv
Date: Fri, 24 Nov 2023 18:08:08 -0800 [thread overview]
Message-ID: <0000000000004d4716060af08a45@google.com> (raw)
In-Reply-To: <00000000000092672f06042b7711@google.com>
syzbot has bisected this issue to:
commit a5b8a5f9f8355d27a4f8d0afa93427f16d2f3c1e
Author: Anand Jain <anand.jain@oracle.com>
Date: Thu Sep 28 01:09:47 2023 +0000
btrfs: support cloned-device mount capability
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1446d344e80000
start commit: d3fa86b1a7b4 Merge tag 'net-6.7-rc3' of git://git.kernel.o..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1646d344e80000
console output: https://syzkaller.appspot.com/x/log.txt?x=1246d344e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=6ae1a4ee971a7305
dashboard link: https://syzkaller.appspot.com/bug?extid=10d5b62a8d7046b86d22
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1431040ce80000
Reported-by: syzbot+10d5b62a8d7046b86d22@syzkaller.appspotmail.com
Fixes: a5b8a5f9f835 ("btrfs: support cloned-device mount capability")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-11-25 2:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 22:29 [syzbot] [btrfs?] WARNING in btrfs_use_block_rsv syzbot
2023-11-25 2:08 ` syzbot [this message]
2023-11-25 22:59 ` Anand Jain
2023-11-28 16:40 ` David Sterba
2023-11-28 18:09 ` Aleksandr Nogikh
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=0000000000004d4716060af08a45@google.com \
--to=syzbot+10d5b62a8d7046b86d22@syzkaller.appspotmail.com \
--cc=anand.jain@oracle.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=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.