From: syzbot <syzbot+7b1677fecb5976b0a099@syzkaller.appspotmail.com>
To: clm@fb.com, davem@davemloft.net, dsterba@suse.com,
johan.hedberg@gmail.com, josef@toxicpanda.com, kuba@kernel.org,
linux-bluetooth@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-kernel@vger.kernel.org, marcel@holtmann.org,
nborisov@suse.com, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: use-after-free Write in hci_conn_del
Date: Mon, 10 Aug 2020 20:35:08 -0700 [thread overview]
Message-ID: <000000000000f7ec6f05ac91c11d@google.com> (raw)
In-Reply-To: <000000000000734f2505ac0f2426@google.com>
syzbot has bisected this issue to:
commit 6a3c7f5c87854e948c3c234e5f5e745c7c553722
Author: Nikolay Borisov <nborisov@suse.com>
Date: Thu May 28 08:05:13 2020 +0000
btrfs: don't balance btree inode pages from buffered write path
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14f973c2900000
start commit: 5631c5e0 Merge tag 'xfs-5.9-merge-7' of git://git.kernel.o..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=16f973c2900000
console output: https://syzkaller.appspot.com/x/log.txt?x=12f973c2900000
kernel config: https://syzkaller.appspot.com/x/.config?x=afba7c06f91e56eb
dashboard link: https://syzkaller.appspot.com/bug?extid=7b1677fecb5976b0a099
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=155d73fa900000
Reported-by: syzbot+7b1677fecb5976b0a099@syzkaller.appspotmail.com
Fixes: 6a3c7f5c8785 ("btrfs: don't balance btree inode pages from buffered write path")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-08-11 3:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 15:45 KASAN: use-after-free Write in hci_conn_del syzbot
2020-08-11 3:35 ` syzbot [this message]
2020-08-11 6:50 ` 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=000000000000f7ec6f05ac91c11d@google.com \
--to=syzbot+7b1677fecb5976b0a099@syzkaller.appspotmail.com \
--cc=clm@fb.com \
--cc=davem@davemloft.net \
--cc=dsterba@suse.com \
--cc=johan.hedberg@gmail.com \
--cc=josef@toxicpanda.com \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=nborisov@suse.com \
--cc=netdev@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).