linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+d93dff37e6a89431c158@syzkaller.appspotmail.com>
To: andreyknvl@google.com, linux-media@vger.kernel.org,
	linux-usb@vger.kernel.org, oneukum@suse.com,
	syzkaller-bugs@googlegroups.com
Subject: Re: general protection fault in flexcop_usb_probe
Date: Mon, 29 Jul 2019 10:34:00 -0700	[thread overview]
Message-ID: <0000000000002b0f41058ed54cf4@google.com> (raw)
In-Reply-To: <CAAeHK+yY3JWAj+EZ5wzqUOMbN+cdddCoRn7Nxn759-7zR-J7BQ@mail.gmail.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger  
crash:

Reported-and-tested-by:  
syzbot+d93dff37e6a89431c158@syzkaller.appspotmail.com

Tested on:

commit:         9a33b369 usb-fuzzer: main usb gadget fuzzer driver
git tree:       https://github.com/google/kasan.git
kernel config:  https://syzkaller.appspot.com/x/.config?x=23e37f59d94ddd15
compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
patch:          https://syzkaller.appspot.com/x/patch.diff?x=11cc12d8600000

Note: testing is done by a robot and is best-effort only.

  reply	other threads:[~2019-07-29 17:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-29 14:26 KASAN reporting: general protection fault in flexcop_usb_probe Oliver Neukum
2019-07-29 15:05 ` syzbot
2019-07-29 16:54   ` Andrey Konovalov
2019-07-29 17:34     ` syzbot [this message]
2019-07-30  7:51     ` Oliver Neukum
2019-07-30  8:52       ` Dmitry Vyukov
  -- strict thread matches above, loose matches on Subject: below --
2019-07-30  7:48 KASAN reporting: " Oliver Neukum
2019-07-30  8:30 ` syzbot
2019-09-20 16:01   ` Andrey Konovalov
2019-09-23  9:06     ` Oliver Neukum
2019-09-23 12:46       ` Andrey Konovalov
2019-09-23 12:51         ` Hans Verkuil
2019-11-07 15:02           ` Oliver Neukum
2019-11-07 15:47             ` Hans Verkuil
2019-11-08  9:07               ` Sean Young
2019-04-12 11:16 syzbot

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=0000000000002b0f41058ed54cf4@google.com \
    --to=syzbot+d93dff37e6a89431c158@syzkaller.appspotmail.com \
    --cc=andreyknvl@google.com \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.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 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).