From: Pavel Machek <pavel@denx.de>
To: syzbot <syzbot+b156665cf4d1b5e00c76@syzkaller.appspotmail.com>
Cc: andreyknvl@google.com, gregkh@linuxfoundation.org,
len.brown@intel.com, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, linux-usb@vger.kernel.org,
rjw@rjwysocki.net, syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: use-after-free Read in __pm_runtime_resume
Date: Fri, 2 Aug 2019 15:33:17 +0200 [thread overview]
Message-ID: <20190802133317.GA5538@amd> (raw)
In-Reply-To: <000000000000cd0435058f21e8c3@google.com>
[-- Attachment #1: Type: text/plain, Size: 929 bytes --]
On Fri 2019-08-02 05:58:05, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: e96407b4 usb-fuzzer: main usb gadget fuzzer driver
> git tree: https://github.com/google/kasan.git usb-fuzzer
> console output: https://syzkaller.appspot.com/x/log.txt?x=146071b4600000
> kernel config: https://syzkaller.appspot.com/x/.config?x=792eb47789f57810
> dashboard link: https://syzkaller.appspot.com/bug?extid=b156665cf4d1b5e00c76
> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
>
> Unfortunately, I don't have any reproducer for this crash yet.
I asked a question, noone bothered to reply, yet you spam me again?
You are a bad bot. Go away. Come back when your human master is
willing to communicate.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2019-08-02 13:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-02 12:58 KASAN: use-after-free Read in __pm_runtime_resume syzbot
2019-08-02 13:33 ` Pavel Machek [this message]
2019-08-02 14:13 ` Andrey Konovalov
[not found] <20190803091232.1836-1-hdanton@sina.com>
2019-08-12 14:26 ` Andrey Konovalov
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=20190802133317.GA5538@amd \
--to=pavel@denx.de \
--cc=andreyknvl@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=syzbot+b156665cf4d1b5e00c76@syzkaller.appspotmail.com \
--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.