public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: syzbot <syzbot+5f1d24c49c1d2c427497@syzkaller.appspotmail.com>
Cc: andreyknvl@google.com, balbi@kernel.org,
	ingrassia@epigenesys.com, linux-kernel@vger.kernel.org,
	linux-usb@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: WARNING in snd_usbmidi_submit_urb/usb_submit_urb
Date: Wed, 3 Jun 2020 08:12:51 +0200	[thread overview]
Message-ID: <20200603061251.GA531505@kroah.com> (raw)
In-Reply-To: <0000000000000eb4b905a7277a7d@google.com>

On Tue, Jun 02, 2020 at 10:41:16PM -0700, syzbot wrote:
> syzbot has found a reproducer for the following crash on:
> 
> HEAD commit:    1ee08de1 Merge tag 'for-5.8/io_uring-2020-06-01' of git://..
> git tree:       upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=15f9e516100000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=b46ebd806238a886
> dashboard link: https://syzkaller.appspot.com/bug?extid=5f1d24c49c1d2c427497
> compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
> userspace arch: i386
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1667dcca100000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=13f9e516100000
> 
> The bug was bisected to:
> 
> commit f2c2e717642c66f7fe7e5dd69b2e8ff5849f4d10
> Author: Andrey Konovalov <andreyknvl@google.com>
> Date:   Mon Feb 24 16:13:03 2020 +0000
> 
>     usb: gadget: add raw-gadget interface

I thought this "bisect to the tool that finds bugs" issue was fixed :)


  reply	other threads:[~2020-06-03  6:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-01  3:56 WARNING in snd_usbmidi_submit_urb/usb_submit_urb syzbot
2020-06-01  7:24 ` syzbot
2020-06-01  8:43   ` Greg KH
2020-06-01 12:22     ` Andrey Konovalov
2020-06-01 12:28       ` Greg KH
2020-06-02 17:19         ` Andrey Konovalov
2020-06-03  5:41 ` syzbot
2020-06-03  6:12   ` Greg KH [this message]
2020-06-03 15:21     ` 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=20200603061251.GA531505@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=andreyknvl@google.com \
    --cc=balbi@kernel.org \
    --cc=ingrassia@epigenesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=syzbot+5f1d24c49c1d2c427497@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox