From: syzbot <syzbot+ee90502d5c8fd1d0dd93@syzkaller.appspotmail.com>
To: boris@bur.io, clm@fb.com, dsterba@suse.com, hch@infradead.org,
hch@lst.de, 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_split_ordered_extent
Date: Thu, 08 Jun 2023 01:40:27 -0700 [thread overview]
Message-ID: <00000000000042bb6e05fd9a3406@google.com> (raw)
In-Reply-To: <00000000000009ee1005fc425b4b@google.com>
syzbot has bisected this issue to:
commit b73a6fd1b1efd799c6e3d14a922887f4453fea17
Author: Boris Burkov <boris@bur.io>
Date: Tue Mar 28 05:19:57 2023 +0000
btrfs: split partial dio bios before submit
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13b24d59280000
start commit: a27648c74210 afs: Fix setting of mtime when creating a fil..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=10724d59280000
console output: https://syzkaller.appspot.com/x/log.txt?x=17b24d59280000
kernel config: https://syzkaller.appspot.com/x/.config?x=7474de833c217bf4
dashboard link: https://syzkaller.appspot.com/bug?extid=ee90502d5c8fd1d0dd93
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=120b88fd280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17e6a23b280000
Reported-by: syzbot+ee90502d5c8fd1d0dd93@syzkaller.appspotmail.com
Fixes: b73a6fd1b1ef ("btrfs: split partial dio bios before submit")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-06-08 8:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 6:26 [syzbot] [btrfs?] WARNING in btrfs_split_ordered_extent syzbot
2023-06-07 23:45 ` syzbot
2023-06-08 7:05 ` Christoph Hellwig
2023-06-08 8:55 ` syzbot
2023-06-08 8:40 ` 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=00000000000042bb6e05fd9a3406@google.com \
--to=syzbot+ee90502d5c8fd1d0dd93@syzkaller.appspotmail.com \
--cc=boris@bur.io \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--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).