From: syzbot <syzbot+843efa30c8821bd69f53@syzkaller.appspotmail.com>
To: Thinh.Nguyen@synopsys.com, felipe.balbi@linux.intel.com,
garsilva@embeddedor.com, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
stern@rowland.harvard.edu, syzkaller-bugs@googlegroups.com,
tiwai@suse.de
Subject: WARNING in usb_submit_urb (2)
Date: Mon, 03 Sep 2018 11:01:02 -0700 [thread overview]
Message-ID: <0000000000000d02c30574fb5364@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: 58c3f14f86c9 Merge tag 'riscv-for-linus-4.19-rc2' of git:/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=175be2b6400000
kernel config: https://syzkaller.appspot.com/x/.config?x=531a917630d2a492
dashboard link: https://syzkaller.appspot.com/bug?extid=843efa30c8821bd69f53
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1526e5c1400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=149b727a400000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+843efa30c8821bd69f53@syzkaller.appspotmail.com
random: sshd: uninitialized urandom read (32 bytes read)
random: sshd: uninitialized urandom read (32 bytes read)
IPVS: ftp: loaded support on port[0] = 21
------------[ cut here ]------------
usb usb1: BOGUS urb flags, 40 --> 0
WARNING: CPU: 1 PID: 4674 at drivers/usb/core/urb.c:503
usb_submit_urb+0x719/0x14d0 drivers/usb/core/urb.c:502
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 4674 Comm: syz-executor803 Not tainted 4.19.0-rc1+ #215
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1c9/0x2b4 lib/dump_stack.c:113
panic+0x238/0x4e7 kernel/panic.c:184
__warn.cold.8+0x163/0x1ba kernel/panic.c:536
report_bug+0x252/0x2d0 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:178 [inline]
do_error_trap+0x1fc/0x4d0 arch/x86/kernel/traps.c:296
do_invalid_op+0x1b/0x20 arch/x86/kernel/traps.c:316
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:993
RIP: 0010:usb_submit_urb+0x719/0x14d0 drivers/usb/core/urb.c:502
Code: 08 fd 48 8b 45 d0 48 8d b8 a0 00 00 00 e8 1f ce 72 ff 45 89 e0 44 89
e9 4c 89 fa 48 89 c6 48 c7 c7 40 d8 7d 87 e8 57 ec d2 fc <0f> 0b e8 30 29
08 fd 48 c7 c6 40 d9 7d 87 4c 89 f7 e8 71 2a 08 fd
RSP: 0018:ffff8801b6e5f278 EFLAGS: 00010282
RAX: 0000000000000000 RBX: ffff8801d38ae500 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff8163ac01 RDI: ffff8801b6e5ef68
RBP: ffff8801b6e5f2e8 R08: ffff8801b6f30100 R09: 0000000000000006
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000040 R14: 0000000000000000 R15: ffff8801ceb80ac0
proc_do_submiturb+0x2669/0x3d70 drivers/usb/core/devio.c:1763
proc_submiturb_compat+0x544/0x800 drivers/usb/core/devio.c:1997
usbdev_do_ioctl+0x19a5/0x3b30 drivers/usb/core/devio.c:2474
usbdev_ioctl+0x25/0x30 drivers/usb/core/devio.c:2551
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:501 [inline]
do_vfs_ioctl+0x1de/0x1720 fs/ioctl.c:685
ksys_ioctl+0xa9/0xd0 fs/ioctl.c:702
__do_sys_ioctl fs/ioctl.c:709 [inline]
__se_sys_ioctl fs/ioctl.c:707 [inline]
__x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:707
do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x444799
Code: 25 02 00 85 c0 b8 00 00 00 00 48 0f 44 c3 5b c3 90 48 89 f8 48 89 f7
48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff
ff 0f 83 2b d7 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00000000007eff78 EFLAGS: 00000213 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007ffdb22eee60 RCX: 0000000000444799
RDX: 0000000020000080 RSI: 00000000802c550a RDI: 0000000000000003
RBP: 0000000000000000 R08: 0000000120080522 R09: 0000000120080522
R10: 000000000000000f R11: 0000000000000213 R12: 0000000000402350
R13: 00000000004023e0 R14: 0000000000000000 R15: 0000000000000000
Dumping ftrace buffer:
(ftrace buffer empty)
Kernel Offset: disabled
Rebooting in 86400 seconds..
---
This bug is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with
syzbot.
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches
reply other threads:[~2018-09-03 18:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=0000000000000d02c30574fb5364@google.com \
--to=syzbot+843efa30c8821bd69f53@syzkaller.appspotmail.com \
--cc=Thinh.Nguyen@synopsys.com \
--cc=felipe.balbi@linux.intel.com \
--cc=garsilva@embeddedor.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tiwai@suse.de \
/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.