From: syzbot <syzbot+06006fc4a90bff8e8f17@syzkaller.appspotmail.com>
To: axboe@kernel.dk, clm@fb.com, dsterba@suse.com, hch@lst.de,
josef@toxicpanda.com, linux-btrfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
senozhatsky@chromium.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [btrfs?] kernel BUG in __extent_writepage_io
Date: Wed, 13 Dec 2023 11:15:03 -0800 [thread overview]
Message-ID: <000000000000fac6ee060c68fb16@google.com> (raw)
In-Reply-To: <000000000000169326060971d07a@google.com>
syzbot has bisected this issue to:
commit 95848dcb9d676738411a8ff70a9704039f1b3982
Author: Christoph Hellwig <hch@lst.de>
Date: Sat Aug 5 05:55:37 2023 +0000
zram: take device and not only bvec offset into account
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1325355ce80000
start commit: eaadbbaaff74 Merge tag 'fuse-fixes-6.7-rc6' of git://git.k..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=10a5355ce80000
console output: https://syzkaller.appspot.com/x/log.txt?x=1725355ce80000
kernel config: https://syzkaller.appspot.com/x/.config?x=53ec3da1d259132f
dashboard link: https://syzkaller.appspot.com/bug?extid=06006fc4a90bff8e8f17
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12cc9deae80000
Reported-by: syzbot+06006fc4a90bff8e8f17@syzkaller.appspotmail.com
Fixes: 95848dcb9d67 ("zram: take device and not only bvec offset into account")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-12-13 19:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 1:31 [syzbot] [btrfs?] kernel BUG in __extent_writepage_io syzbot
2023-12-13 1:58 ` syzbot
2023-12-13 19:15 ` syzbot [this message]
2024-05-15 16:36 ` 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=000000000000fac6ee060c68fb16@google.com \
--to=syzbot+06006fc4a90bff8e8f17@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=hch@lst.de \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=senozhatsky@chromium.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