From: syzbot <syzbot+b70e32fc4c6568d6d19e@syzkaller.appspotmail.com>
To: bernie@plugable.com, dri-devel@lists.freedesktop.org,
linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] WARNING in dlfb_set_video_mode/usb_submit_urb
Date: Sat, 05 Jun 2021 06:00:19 -0700 [thread overview]
Message-ID: <000000000000f7365905c4046327@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: c2131f7e Merge tag 'gfs2-v5.13-rc2-fixes' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1204b5d3d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=e2ecf1aa681aadc1
dashboard link: https://syzkaller.appspot.com/bug?extid=b70e32fc4c6568d6d19e
compiler: Debian clang version 11.0.1-2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15282db7d00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1763504dd00000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+b70e32fc4c6568d6d19e@syzkaller.appspotmail.com
usb 1-1: Read EDID byte 0 failed: -71
usb 1-1: Read EDID byte 0 failed: -71
usb 1-1: Read EDID byte 0 failed: -71
usb 1-1: Unable to get valid EDID from device/display
------------[ cut here ]------------
usb 1-1: BOGUS urb xfer, pipe 3 != type 1
WARNING: CPU: 0 PID: 8629 at drivers/usb/core/urb.c:494 usb_submit_urb+0xacd/0x1550 drivers/usb/core/urb.c:493
Modules linked in:
CPU: 0 PID: 8629 Comm: kworker/0:4 Not tainted 5.13.0-rc4-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: usb_hub_wq hub_event
RIP: 0010:usb_submit_urb+0xacd/0x1550 drivers/usb/core/urb.c:493
Code: d8 48 c1 e8 03 42 8a 04 28 84 c0 0f 85 bd 07 00 00 44 8b 03 48 c7 c7 80 86 e1 8a 4c 89 f6 4c 89 fa 89 e9 31 c0 e8 63 c7 8f fb <0f> 0b 4c 8b 74 24 30 45 89 f7 4c 89 ff 48 c7 c6 70 e1 8d 8d e8 6a
RSP: 0018:ffffc90001f36660 EFLAGS: 00010246
RAX: 0baf7fe5b4c01b00 RBX: ffffffff8ae184ac RCX: ffff888035c09c40
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: 0000000000000003 R08: ffffffff81655632 R09: ffffed1017345f90
R10: ffffed1017345f90 R11: 0000000000000000 R12: ffff888017813700
R13: dffffc0000000000 R14: ffffffff8ae226e0 R15: ffff888017212b90
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fe721263740 CR3: 0000000017ff3000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
dlfb_submit_urb drivers/video/fbdev/udlfb.c:1969 [inline]
dlfb_set_video_mode+0x1b2a/0x3500 drivers/video/fbdev/udlfb.c:315
dlfb_ops_set_par+0x731/0xb50 drivers/video/fbdev/udlfb.c:1110
dlfb_usb_probe+0x184e/0x21b0 drivers/video/fbdev/udlfb.c:1732
usb_probe_interface+0x633/0xb40 drivers/usb/core/driver.c:396
really_probe+0x3cb/0x1020 drivers/base/dd.c:580
driver_probe_device+0x178/0x350 drivers/base/dd.c:763
bus_for_each_drv+0x16a/0x1f0 drivers/base/bus.c:431
__device_attach+0x301/0x560 drivers/base/dd.c:938
bus_probe_device+0xb8/0x1f0 drivers/base/bus.c:491
device_add+0x11fc/0x1670 drivers/base/core.c:3324
usb_set_configuration+0x1a86/0x2100 drivers/usb/core/message.c:2164
usb_generic_driver_probe+0x83/0x140 drivers/usb/core/generic.c:238
usb_probe_device+0x13a/0x260 drivers/usb/core/driver.c:293
really_probe+0x3cb/0x1020 drivers/base/dd.c:580
driver_probe_device+0x178/0x350 drivers/base/dd.c:763
bus_for_each_drv+0x16a/0x1f0 drivers/base/bus.c:431
__device_attach+0x301/0x560 drivers/base/dd.c:938
bus_probe_device+0xb8/0x1f0 drivers/base/bus.c:491
device_add+0x11fc/0x1670 drivers/base/core.c:3324
usb_new_device+0xd45/0x1790 drivers/usb/core/hub.c:2556
hub_port_connect+0x1055/0x27a0 drivers/usb/core/hub.c:5276
hub_port_connect_change+0x5d0/0xbf0 drivers/usb/core/hub.c:5416
port_event+0xaee/0x1140 drivers/usb/core/hub.c:5562
hub_event+0x48d/0xd90 drivers/usb/core/hub.c:5644
process_one_work+0x833/0x10c0 kernel/workqueue.c:2276
worker_thread+0xac1/0x1300 kernel/workqueue.c:2422
kthread+0x39a/0x3c0 kernel/kthread.c:313
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294
---
This report 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 issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
reply other threads:[~2021-06-05 13:00 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=000000000000f7365905c4046327@google.com \
--to=syzbot+b70e32fc4c6568d6d19e@syzkaller.appspotmail.com \
--cc=bernie@plugable.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@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.