From: syzbot <syzbot+5b82f0e951f8c2bcdb8f@syzkaller.appspotmail.com>
To: clm@fb.com, dsterba@suse.com, 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?] general protection fault in btrfs_finish_ordered_extent
Date: Thu, 13 Jul 2023 18:43:24 -0700 [thread overview]
Message-ID: <00000000000012a70f0600689326@google.com> (raw)
In-Reply-To: <0000000000003735c9060061384a@google.com>
syzbot has bisected this issue to:
commit b41b6f6937dc89e072b334e8d814487cb4692770
Author: Christoph Hellwig <hch@lst.de>
Date: Wed May 31 07:54:09 2023 +0000
btrfs: use btrfs_finish_ordered_extent to complete direct writes
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14761374a80000
start commit: 1c7873e33645 mm: lock newly mapped VMA with corrected orde..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=16761374a80000
console output: https://syzkaller.appspot.com/x/log.txt?x=12761374a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=9831e2c2660aae77
dashboard link: https://syzkaller.appspot.com/bug?extid=5b82f0e951f8c2bcdb8f
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=109dcf08a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13dadfb4a80000
Reported-by: syzbot+5b82f0e951f8c2bcdb8f@syzkaller.appspotmail.com
Fixes: b41b6f6937dc ("btrfs: use btrfs_finish_ordered_extent to complete direct writes")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-07-14 1:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 16:56 [syzbot] [btrfs?] general protection fault in btrfs_finish_ordered_extent syzbot
2023-07-14 1:43 ` 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=00000000000012a70f0600689326@google.com \
--to=syzbot+5b82f0e951f8c2bcdb8f@syzkaller.appspotmail.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--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).