From: syzbot <syzbot+a66a7c2e996797bb4acb@syzkaller.appspotmail.com>
To: davem@davemloft.net, festevam@gmail.com,
gregkh@linuxfoundation.org, grundler@chromium.org,
hayeswang@realtek.com, johan.hedberg@gmail.com,
kernel@pengutronix.de, linux-arm-kernel@lists.infradead.org,
linux-bluetooth@vger.kernel.org, linux-imx@nxp.com,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
marcel@holtmann.org, nishadkamdar@gmail.com, peter.chen@nxp.com,
pmalani@chromium.org, s.hauer@pengutronix.de,
shawnguo@kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: use-after-free Read in skb_release_data (2)
Date: Tue, 31 Mar 2020 10:36:01 -0700 [thread overview]
Message-ID: <0000000000005b022005a22a0050@google.com> (raw)
In-Reply-To: <000000000000da6059059fcfdcf9@google.com>
syzbot suspects this bug was fixed by commit:
commit d9958306d4be14f4c7466242b38ed3893a7b1386
Author: Nishad Kamdar <nishadkamdar@gmail.com>
Date: Sun Mar 15 10:55:07 2020 +0000
USB: chipidea: Use the correct style for SPDX License Identifier
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16d4940be00000
start commit: 63623fd4 Merge tag 'for-linus' of git://git.kernel.org/pub..
git tree: upstream
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
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: USB: chipidea: Use the correct style for SPDX License Identifier
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next parent reply other threads:[~2020-03-31 17:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000da6059059fcfdcf9@google.com>
2020-03-31 17:36 ` syzbot [this message]
2020-03-31 17:41 ` KASAN: use-after-free Read in skb_release_data (2) Greg KH
2020-03-31 17:44 ` Grant Grundler
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=0000000000005b022005a22a0050@google.com \
--to=syzbot+a66a7c2e996797bb4acb@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=grundler@chromium.org \
--cc=hayeswang@realtek.com \
--cc=johan.hedberg@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=nishadkamdar@gmail.com \
--cc=peter.chen@nxp.com \
--cc=pmalani@chromium.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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).