From: syzbot <syzbot+e864a35d361e1d4e29a5@syzkaller.appspotmail.com>
To: anand.jain@oracle.com, clm@fb.com, dsterba@suse.com,
johannes.thumshirn@wdc.com, josef@toxicpanda.com,
jthumshirn@suse.de, linux-btrfs@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: kernel BUG at lib/string.c:LINE! (5)
Date: Wed, 16 Sep 2020 01:19:10 -0700 [thread overview]
Message-ID: <0000000000000bcff305af69ecae@google.com> (raw)
In-Reply-To: <000000000000a61d6b05af580e62@google.com>
syzbot has bisected this issue to:
commit 3951e7f050ac6a38bbc859fc3cd6093890c31d1c
Author: Johannes Thumshirn <jthumshirn@suse.de>
Date: Mon Oct 7 09:11:01 2019 +0000
btrfs: add xxhash64 to checksumming algorithms
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10aadcc5900000
start commit: e4c26faa Merge tag 'usb-5.9-rc5' of git://git.kernel.org/p..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=12aadcc5900000
console output: https://syzkaller.appspot.com/x/log.txt?x=14aadcc5900000
kernel config: https://syzkaller.appspot.com/x/.config?x=c61610091f4ca8c4
dashboard link: https://syzkaller.appspot.com/bug?extid=e864a35d361e1d4e29a5
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=177582be900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13deb2b5900000
Reported-by: syzbot+e864a35d361e1d4e29a5@syzkaller.appspotmail.com
Fixes: 3951e7f050ac ("btrfs: add xxhash64 to checksumming algorithms")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-09-16 8:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 11:00 kernel BUG at lib/string.c:LINE! (5) syzbot
2020-09-16 8:19 ` syzbot [this message]
2020-09-16 8:45 ` Johannes Thumshirn
2020-09-17 13:14 ` 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=0000000000000bcff305af69ecae@google.com \
--to=syzbot+e864a35d361e1d4e29a5@syzkaller.appspotmail.com \
--cc=anand.jain@oracle.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=johannes.thumshirn@wdc.com \
--cc=josef@toxicpanda.com \
--cc=jthumshirn@suse.de \
--cc=linux-btrfs@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.