All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+cabfa4b5b05ff6be4ef0@syzkaller.appspotmail.com>
To: andreyknvl@google.com, hverkuil-cisco@xs4all.nl,
	linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	linux-usb@vger.kernel.org, mchehab@kernel.org, oneukum@suse.com,
	syzkaller-bugs@googlegroups.com
Subject: Re: general protection fault in go7007_usb_probe
Date: Thu, 23 Apr 2020 06:05:05 -0700	[thread overview]
Message-ID: <000000000000c0064305a3f4e57b@google.com> (raw)
In-Reply-To: <1587645997.23108.9.camel@suse.com>

Hello,

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

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

Tested on:

commit:         e9010320 usb: cdns3: gadget: make a bunch of functions sta..
git tree:       https://github.com/google/kasan.git
kernel config:  https://syzkaller.appspot.com/x/.config?x=bd14feb44652cfaf
dashboard link: https://syzkaller.appspot.com/bug?extid=cabfa4b5b05ff6be4ef0
compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
patch:          https://syzkaller.appspot.com/x/patch.diff?x=1396d5bfe00000

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

  reply	other threads:[~2020-04-23 13:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21 23:36 general protection fault in go7007_usb_probe syzbot
2020-04-21 23:45 ` syzbot
2020-04-22 10:32   ` Oliver Neukum
2020-04-22 10:51     ` Takashi Iwai
2020-04-22 11:59 ` Oliver Neukum
2020-04-22 12:32   ` syzbot
2020-04-23 11:01 ` Oliver Neukum
2020-04-23 11:20   ` syzbot
2020-04-23 12:46 ` Oliver Neukum
2020-04-23 13:05   ` syzbot [this message]
2020-04-23 13:48 ` Oliver Neukum
2020-04-23 13:59   ` syzbot
2020-04-30 13:09 ` Oliver Neukum
2020-04-30 13:29   ` syzbot
2020-05-04 14:08 ` Oliver Neukum
2020-05-04 14:27   ` 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=000000000000c0064305a3f4e57b@google.com \
    --to=syzbot+cabfa4b5b05ff6be4ef0@syzkaller.appspotmail.com \
    --cc=andreyknvl@google.com \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mchehab@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 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.