From: syzbot <syzbot+7634edaea4d0b341c625@syzkaller.appspotmail.com>
To: andreyknvl@google.com, linux-usb@vger.kernel.org,
stern@rowland.harvard.edu, syzkaller-bugs@googlegroups.com
Subject: WARNING in usb_submit_urb (4)
Date: Thu, 18 Apr 2019 11:29:00 -0700 [thread overview]
Message-ID: <0000000000000fa8360586d22dd5@google.com> (raw)
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger
crash:
Reported-and-tested-by:
syzbot+7634edaea4d0b341c625@syzkaller.appspotmail.com
Tested on:
commit: e12e00e3 Merge tag 'kbuild-fixes-v4.20' of git://git.kerne..
git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel config: https://syzkaller.appspot.com/x/.config?x=69667e62a5e247a7
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
patch: https://syzkaller.appspot.com/x/patch.diff?x=17a7eaa0a00000
Note: testing is done by a robot and is best-effort only.
WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+7634edaea4d0b341c625@syzkaller.appspotmail.com>
To: andreyknvl@google.com, linux-usb@vger.kernel.org,
stern@rowland.harvard.edu, syzkaller-bugs@googlegroups.com
Subject: Re: WARNING in usb_submit_urb (4)
Date: Thu, 18 Apr 2019 11:29:00 -0700 [thread overview]
Message-ID: <0000000000000fa8360586d22dd5@google.com> (raw)
Message-ID: <20190418182900.xYf91C2MPx3waONCw1w4Enjt9V_KMupf4g5SSqLXdFw@z> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1904181405430.1303-100000@iolanthe.rowland.org>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger
crash:
Reported-and-tested-by:
syzbot+7634edaea4d0b341c625@syzkaller.appspotmail.com
Tested on:
commit: e12e00e3 Merge tag 'kbuild-fixes-v4.20' of git://git.kerne..
git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel config: https://syzkaller.appspot.com/x/.config?x=69667e62a5e247a7
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
patch: https://syzkaller.appspot.com/x/patch.diff?x=17a7eaa0a00000
Note: testing is done by a robot and is best-effort only.
next prev reply other threads:[~2019-04-18 18:29 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAeHK+y0D9YJB5=N6ET-ECsLejnzBNUZOeQuOv+p7aRGiMEGTA@mail.gmail.com>
2019-04-16 17:39 ` WARNING in usb_submit_urb (4) Alan Stern
2019-04-16 17:39 ` Alan Stern
2019-04-16 17:53 ` syzbot
2019-04-16 17:53 ` syzbot
2019-04-16 19:10 ` Alan Stern
2019-04-16 19:10 ` Alan Stern
2019-04-16 19:33 ` syzbot
2019-04-16 19:33 ` syzbot
2019-04-16 20:57 ` Alan Stern
2019-04-16 20:57 ` Alan Stern
2019-04-16 21:10 ` syzbot
2019-04-16 21:10 ` syzbot
2019-04-17 20:59 ` Alan Stern
2019-04-17 20:59 ` Alan Stern
2019-04-17 21:12 ` syzbot
2019-04-17 21:12 ` syzbot
2019-04-18 16:00 ` Alan Stern
2019-04-18 16:00 ` Alan Stern
2019-04-18 16:53 ` Alan Stern
2019-04-18 16:53 ` Alan Stern
2019-04-18 17:41 ` syzbot
2019-04-18 17:41 ` syzbot
2019-04-18 18:09 ` Alan Stern
2019-04-18 18:09 ` Alan Stern
2019-04-18 18:29 ` syzbot [this message]
2019-04-18 18:29 ` syzbot
2019-04-18 20:04 ` Alan Stern
2019-04-18 20:04 ` Alan Stern
2019-04-18 20:24 ` syzbot
2019-04-18 20:24 ` syzbot
[not found] <00000000000065a79f057a095de8@google.com>
2019-04-11 1:01 ` 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=0000000000000fa8360586d22dd5@google.com \
--to=syzbot+7634edaea4d0b341c625@syzkaller.appspotmail.com \
--cc=andreyknvl@google.com \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--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