All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+e87ebe0f7913f71f2ea5@syzkaller.appspotmail.com>
To: andreyknvl@google.com, gregkh@linuxfoundation.org,
	johan@kernel.org, linux-kernel@vger.kernel.org,
	linux-usb@vger.kernel.org, stable@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: WARNING in yurex_write/usb_submit_urb
Date: Mon, 14 Dec 2020 12:12:03 -0800	[thread overview]
Message-ID: <00000000000069fb4f05b6724198@google.com> (raw)
In-Reply-To: <X9eB5ZZMq6q5j4eW@localhost>

Hello,

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

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

Tested on:

commit:         a256e240 usb: phy: convert comma to semicolon
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
kernel config:  https://syzkaller.appspot.com/x/.config?x=4536e7f93c2bc8e9
dashboard link: https://syzkaller.appspot.com/bug?extid=e87ebe0f7913f71f2ea5
compiler:       gcc (GCC) 10.1.0-syz 20200507
patch:          https://syzkaller.appspot.com/x/patch.diff?x=11a9f703500000

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

  reply	other threads:[~2020-12-14 20:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-12 22:33 WARNING in yurex_write/usb_submit_urb syzbot
2020-12-13 20:31 ` syzbot
2020-12-14 10:44   ` [PATCH] USB: yurex: fix control-URB timeout handling Johan Hovold
2020-12-14 10:50     ` Johan Hovold
2020-12-14 14:48       ` WARNING in yurex_write/usb_submit_urb syzbot
2020-12-14 15:02         ` Johan Hovold
2020-12-14 15:06           ` Andrey Konovalov
2020-12-14 15:16             ` Johan Hovold
2020-12-14 20:12               ` syzbot [this message]
2020-12-15 14:08               ` Andrey Konovalov
2020-12-14  4:30 ` 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=00000000000069fb4f05b6724198@google.com \
    --to=syzbot+e87ebe0f7913f71f2ea5@syzkaller.appspotmail.com \
    --cc=andreyknvl@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stable@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.