Hello,
syzbot found the following issue on:
HEAD commit: 700e62ea909a Linux 5.15.224
git tree: linux-5.15.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=10999a8d580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=ac990d5ab58b7297
dashboard link:
https://syzkaller.appspot.com/bug?extid=0be5e29be8acba498d9f
compiler: Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/2b1c03915da0/disk-700e62ea.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/11dcf7e1a04e/vmlinux-700e62ea.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/939ee26cf006/bzImage-700e62ea.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+0be5e2...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 13 at drivers/gpu/drm/drm_blend.c:286 drm_plane_create_rotation_property+0x16f/0x1b0 drivers/gpu/drm/drm_blend.c:286
Modules linked in:
CPU: 0 PID: 13 Comm: kworker/0:1 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/07/2026
Workqueue: usb_hub_wq hub_event
RIP: 0010:drm_plane_create_rotation_property+0x16f/0x1b0 drivers/gpu/drm/drm_blend.c:286
Code: 00 48 89 d8 48 c1 e8 03 42 80 3c 20 00 74 08 48 89 df e8 74 b6 4a fd 4c 89 33 31 c0 5b 41 5c 41 5e 41 5f 5d c3 e8 b1 6d 05 fd <0f> 0b e9 bd fe ff ff e8 a5 6d 05 fd 0f 0b e9 ef fe ff ff e8 99 6d
RSP: 0018:ffffc90000d26e30 EFLAGS: 00010287
RAX: ffffffff8473bfdf RBX: ffff88807ab19260 RCX: 0000000000100000
RDX: ffffc90015da6000 RSI: 000000000002e5f4 RDI: 000000000002e5f5
RBP: 0000000000000001 R08: ffffffff8a8ded20 R09: 0000000000000040
R10: dffffc0000000000 R11: fffffbfff2208e27 R12: 0000000000000032
R13: ffff8880218df800 R14: 0000000000000000 R15: 0000000000000096
FS: 0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fd7f36832f8 CR3: 0000000062471000 CR4: 00000000003506f0
Call Trace:
<TASK>
gud_get_properties+0x225/0x3d0 drivers/gpu/drm/gud/gud_drv.c:290
gud_probe+0x10a8/0x16a0 drivers/gpu/drm/gud/gud_drv.c:596
usb_probe_interface+0x5be/0xae0 drivers/usb/core/driver.c:396
call_driver_probe drivers/base/dd.c:-1 [inline]
really_probe+0x276/0xc70 drivers/base/dd.c:595
__driver_probe_device+0x1f5/0x390 drivers/base/dd.c:775
driver_probe_device+0x4f/0x420 drivers/base/dd.c:805
__device_attach_driver+0x2b0/0x500 drivers/base/dd.c:927
bus_for_each_drv+0x184/0x210 drivers/base/bus.c:429
__device_attach+0x2a7/0x480 drivers/base/dd.c:999
bus_probe_device+0xba/0x1d0 drivers/base/bus.c:489
device_add+0xbcf/0x1050 drivers/base/core.c:3427
usb_set_configuration+0x1ad8/0x2140 drivers/usb/core/message.c:2229
usb_generic_driver_probe+0x89/0x150 drivers/usb/core/generic.c:238
usb_probe_device+0x126/0x250 drivers/usb/core/driver.c:293
call_driver_probe drivers/base/dd.c:-1 [inline]
really_probe+0x276/0xc70 drivers/base/dd.c:595
__driver_probe_device+0x1f5/0x390 drivers/base/dd.c:775
driver_probe_device+0x4f/0x420 drivers/base/dd.c:805
__device_attach_driver+0x2b0/0x500 drivers/base/dd.c:927
bus_for_each_drv+0x184/0x210 drivers/base/bus.c:429
__device_attach+0x2a7/0x480 drivers/base/dd.c:999
bus_probe_device+0xba/0x1d0 drivers/base/bus.c:489
device_add+0xbcf/0x1050 drivers/base/core.c:3427
usb_new_device+0x9f6/0x15d0 drivers/usb/core/hub.c:2642
hub_port_connect drivers/usb/core/hub.c:5507 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5647 [inline]
port_event drivers/usb/core/hub.c:5809 [inline]
hub_event+0x2b8d/0x5260 drivers/usb/core/hub.c:5891
process_one_work+0x867/0xff0 kernel/workqueue.c:2310
worker_thread+0xad7/0x12a0 kernel/workqueue.c:2457
kthread+0x42e/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
---
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
syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup