From: syzbot <syzbot+a66a7c2e996797bb4acb@syzkaller.appspotmail.com>
To: davem@davemloft.net, grundler@chromium.org,
hayeswang@realtek.com, johan.hedberg@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
marcel@holtmann.org, pmalani@chromium.org,
syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: use-after-free Read in skb_release_data (2)
Date: Wed, 18 Mar 2020 20:48:03 -0700 [thread overview]
Message-ID: <0000000000002c1d4405a12d0975@google.com> (raw)
In-Reply-To: <000000000000da6059059fcfdcf9@google.com>
syzbot has bisected this bug to:
commit 5f71c84038d39def573744a145c573758f52a949
Author: Prashant Malani <pmalani@chromium.org>
Date: Tue Oct 1 08:35:57 2019 +0000
r8152: Factor out OOB link list waits
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15f5b973e00000
start commit: 63623fd4 Merge tag 'for-linus' of git://git.kernel.org/pub..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=17f5b973e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=13f5b973e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=5d2e033af114153f
dashboard link: https://syzkaller.appspot.com/bug?extid=a66a7c2e996797bb4acb
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13c25a81e00000
Reported-by: syzbot+a66a7c2e996797bb4acb@syzkaller.appspotmail.com
Fixes: 5f71c84038d3 ("r8152: Factor out OOB link list waits")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-03-19 3:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-01 19:13 KASAN: use-after-free Read in skb_release_data (2) syzbot
2020-03-19 3:48 ` syzbot [this message]
2020-03-31 17:36 ` syzbot
2020-03-31 17:36 ` syzbot
2020-03-31 17:41 ` Greg KH
2020-03-31 17:41 ` Greg KH
2020-03-31 17:44 ` Grant Grundler
2020-03-31 17:44 ` Grant Grundler
2020-04-01 9:12 ` Dmitry Vyukov
2020-04-01 9:12 ` Dmitry Vyukov
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=0000000000002c1d4405a12d0975@google.com \
--to=syzbot+a66a7c2e996797bb4acb@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=grundler@chromium.org \
--cc=hayeswang@realtek.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=pmalani@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 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.