All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+53ce4a4246d0fe0fee34@syzkaller.appspotmail.com>
To: andreyknvl@google.com, balbi@kernel.org, corbet@lwn.net,
	gregkh@linuxfoundation.org, gustavo@embeddedor.com,
	ingrassia@epigenesys.com, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: WARNING in dlfb_submit_urb/usb_submit_urb
Date: Sun, 24 May 2020 14:53:03 -0700	[thread overview]
Message-ID: <00000000000000537605a66be3a8@google.com> (raw)
In-Reply-To: <000000000000cd404e058c9de28b@google.com>

syzbot has bisected this bug to:

commit c61769bd4777a922952aed0d042a2572e5bd9b74
Author: Andrey Konovalov <andreyknvl@google.com>
Date:   Thu May 7 17:06:57 2020 +0000

    usb: raw-gadget: support stalling/halting/wedging endpoints

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=14add53c100000
start commit:   051143e1 Merge tag 'apparmor-pr-2020-05-21' of git://git.k..
git tree:       upstream
final crash:    https://syzkaller.appspot.com/x/report.txt?x=16add53c100000
console output: https://syzkaller.appspot.com/x/log.txt?x=12add53c100000
kernel config:  https://syzkaller.appspot.com/x/.config?x=b3368ce0cc5f5ace
dashboard link: https://syzkaller.appspot.com/bug?extid=53ce4a4246d0fe0fee34
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=15be3ad6100000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1559676e100000

Reported-by: syzbot+53ce4a4246d0fe0fee34@syzkaller.appspotmail.com
Fixes: c61769bd4777 ("usb: raw-gadget: support stalling/halting/wedging endpoints")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

      reply	other threads:[~2020-05-24 21:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-01 12:37 WARNING in dlfb_submit_urb/usb_submit_urb syzbot
2020-05-24 21:53 ` syzbot [this message]

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=00000000000000537605a66be3a8@google.com \
    --to=syzbot+53ce4a4246d0fe0fee34@syzkaller.appspotmail.com \
    --cc=andreyknvl@google.com \
    --cc=balbi@kernel.org \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=gustavo@embeddedor.com \
    --cc=ingrassia@epigenesys.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.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 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.