[moderation] [block?] INFO: task poweroff:NUM blocked for more than NUM seconds.
1 view
Skip to first unread message
syzbot
Feb 11, 2026, 2:27:29 AM (23 hours ago) Feb 11
to syzkaller-upst...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 9845cf73f7db Add linux-next specific files for 20260205
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1568fa5a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=ac78ce3b6729749e
dashboard link: https://syzkaller.appspot.com/bug?extid=67eac54e93558f052003
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
CC: [ax...@kernel.dk linux...@vger.kernel.org linux-...@vger.kernel.org]
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9f30334a2431/disk-9845cf73.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0d58741a15a6/vmlinux-9845cf73.xz
kernel image: https://storage.googleapis.com/syzbot-assets/62204da1452c/bzImage-9845cf73.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+67eac5...@syzkaller.appspotmail.com
INFO: task poweroff:6675 blocked for more than 144 seconds.
Tainted: G L syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:poweroff state:D stack:23904 pid:6675 tgid:6675 ppid:5176 task_flags:0x400000 flags:0x00080000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5295 [inline]
__schedule+0x1585/0x5310 kernel/sched/core.c:6907
__schedule_loop kernel/sched/core.c:6989 [inline]
schedule+0x164/0x360 kernel/sched/core.c:7004
schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:7061
__mutex_lock_common kernel/locking/mutex.c:692 [inline]
__mutex_lock+0x7fe/0x1300 kernel/locking/mutex.c:776
sync_bdevs+0x27e/0x470 block/bdev.c:1304
ksys_sync fs/sync.c:105 [inline]
__ia32_sys_sync+0xc5/0x120 fs/sync.c:111
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x14d/0xf80 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fa532cc8f37
RSP: 002b:00007ffcecf9e738 EFLAGS: 00000246 ORIG_RAX: 00000000000000a2
RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007fa532cc8f37
RDX: ffffffffffffff88 RSI: 00007fa532e61e51 RDI: 00000000ffffff9c
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffcecf9e898 R14: 00007fa532eab000 R15: 00005629478cad98
</TASK>
Showing all locks held in the system:
1 lock held by khungtaskd/30:
#0: ffffffff8e960320 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:312 [inline]
#0: ffffffff8e960320 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:850 [inline]
#0: ffffffff8e960320 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x2e/0x180 kernel/locking/lockdep.c:6775
6 locks held by kworker/0:2/796:
#0: ffff888021abb948 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x855/0x1650 kernel/workqueue.c:3254
#1: ffffc90003367c40 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x87c/0x1650 kernel/workqueue.c:3255
#2: ffff888029f45198 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:895 [inline]
#2: ffff888029f45198 (&dev->mutex){....}-{4:4}, at: hub_event+0x17f/0x4f30 drivers/usb/core/hub.c:5899
#3: ffff888029f42518 (&port_dev->status_lock){+.+.}-{4:4}, at: usb_lock_port drivers/usb/core/hub.c:3252 [inline]
#3: ffff888029f42518 (&port_dev->status_lock){+.+.}-{4:4}, at: hub_port_connect drivers/usb/core/hub.c:5464 [inline]
#3: ffff888029f42518 (&port_dev->status_lock){+.+.}-{4:4}, at: hub_port_connect_change drivers/usb/core/hub.c:5707 [inline]
#3: ffff888029f42518 (&port_dev->status_lock){+.+.}-{4:4}, at: port_event drivers/usb/core/hub.c:5871 [inline]
#3: ffff888029f42518 (&port_dev->status_lock){+.+.}-{4:4}, at: hub_event+0x217a/0x4f30 drivers/usb/core/hub.c:5953
#4: ffff888029ec1c68 (hcd->address0_mutex){+.+.}-{4:4}, at: hub_port_connect drivers/usb/core/hub.c:5465 [inline]
#4: ffff888029ec1c68 (hcd->address0_mutex){+.+.}-{4:4}, at: hub_port_connect_change drivers/usb/core/hub.c:5707 [inline]
#4: ffff888029ec1c68 (hcd->address0_mutex){+.+.}-{4:4}, at: port_event drivers/usb/core/hub.c:5871 [inline]
#4: ffff888029ec1c68 (hcd->address0_mutex){+.+.}-{4:4}, at: hub_event+0x21a2/0x4f30 drivers/usb/core/hub.c:5953
#5: ffffffff8f68ef30 (ehci_cf_port_reset_rwsem){.+.+}-{4:4}, at: hub_port_reset+0x14e/0x1840 drivers/usb/core/hub.c:3067
5 locks held by kworker/u8:7/3482:
2 locks held by getty/5581:
#0: ffff88803214d0a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
#1: ffffc9000332b2f0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x45c/0x13c0 drivers/tty/n_tty.c:2211
1 lock held by udevd/5833:
#0: ffff888026cbd358 (&disk->open_mutex){+.+.}-{4:4}, at: bdev_open+0xe0/0xd30 block/bdev.c:961
2 locks held by kworker/0:4/5873:
1 lock held by poweroff/6675:
#0: ffff888026cbd358 (&disk->open_mutex){+.+.}-{4:4}, at: sync_bdevs+0x27e/0x470 block/bdev.c:1304
=============================================
NMI backtrace for cpu 1
CPU: 1 UID: 0 PID: 30 Comm: khungtaskd Tainted: G L syzkaller #0 PREEMPT(full)
Tainted: [L]=SOFTLOCKUP
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/24/2026
Call Trace:
<TASK>
dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
nmi_cpu_backtrace+0x274/0x2d0 lib/nmi_backtrace.c:113
nmi_trigger_cpumask_backtrace+0x17a/0x300 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:161 [inline]
__sys_info lib/sys_info.c:157 [inline]
sys_info+0x135/0x170 lib/sys_info.c:165
check_hung_uninterruptible_tasks kernel/hung_task.c:347 [inline]
watchdog+0x103d/0x1090 kernel/hung_task.c:516
kthread+0x388/0x470 kernel/kthread.c:467
ret_from_fork+0x51e/0xb90 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 796 Comm: kworker/0:2 Tainted: G L syzkaller #0 PREEMPT(full)
Tainted: [L]=SOFTLOCKUP
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/24/2026
Workqueue: usb_hub_wq hub_event
RIP: 0010:io_serial_in+0x77/0xc0 drivers/tty/serial/8250/8250_port.c:400
Code: e8 be f4 7c fc 44 89 f9 d3 e3 49 83 c6 40 4c 89 f0 48 c1 e8 03 42 80 3c 20 00 74 08 4c 89 f7 e8 2f de e6 fc 41 03 1e 89 da ec <0f> b6 c0 5b 41 5c 41 5e 41 5f e9 da 9f 72 06 cc 44 89 f9 80 e1 07
RSP: 0018:ffffc90003367070 EFLAGS: 00000002
RAX: 1ffffffff3503100 RBX: 00000000000003fd RCX: 0000000000000000
RDX: 00000000000003fd RSI: 000000000000f581 RDI: 000000000000f582
RBP: ffffffff9a818ed0 R08: ffff888025aa8237 R09: 1ffff11004b55046
R10: dffffc0000000000 R11: ffffffff8548f8c0 R12: dffffc0000000000
R13: 0000000000000000 R14: ffffffff9a818c40 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff888125015000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005555753eba28 CR3: 0000000078912000 CR4: 00000000003526f0
Call Trace:
<TASK>
serial_in drivers/tty/serial/8250/8250.h:128 [inline]
serial_lsr_in drivers/tty/serial/8250/8250.h:150 [inline]
wait_for_lsr+0x1a1/0x2f0 drivers/tty/serial/8250/8250_port.c:1961
fifo_wait_for_lsr drivers/tty/serial/8250/8250_port.c:3234 [inline]
serial8250_console_fifo_write drivers/tty/serial/8250/8250_port.c:3257 [inline]
serial8250_console_write+0x1348/0x1ba0 drivers/tty/serial/8250/8250_port.c:3342
console_emit_next_record kernel/printk/printk.c:3131 [inline]
console_flush_one_record kernel/printk/printk.c:3217 [inline]
console_flush_all+0x718/0xb20 kernel/printk/printk.c:3291
__console_flush_and_unlock kernel/printk/printk.c:3321 [inline]
console_unlock+0xd1/0x1c0 kernel/printk/printk.c:3361
vprintk_emit+0x485/0x560 kernel/printk/printk.c:2428
dev_vprintk_emit+0x355/0x420 drivers/base/core.c:4914
dev_printk_emit+0xee/0x140 drivers/base/core.c:4925
_dev_info+0x11e/0x180 drivers/base/core.c:4983
hub_port_connect drivers/usb/core/hub.c:5606 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5707 [inline]
port_event drivers/usb/core/hub.c:5871 [inline]
hub_event+0x2d3a/0x4f30 drivers/usb/core/hub.c:5953
process_one_work+0x949/0x1650 kernel/workqueue.c:3279
process_scheduled_works kernel/workqueue.c:3362 [inline]
worker_thread+0xb46/0x1140 kernel/workqueue.c:3443
kthread+0x388/0x470 kernel/kthread.c:467
ret_from_fork+0x51e/0xb90 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</TASK>
----------------
Code disassembly (best guess):
0: e8 be f4 7c fc call 0xfc7cf4c3
5: 44 89 f9 mov %r15d,%ecx
8: d3 e3 shl %cl,%ebx
a: 49 83 c6 40 add $0x40,%r14
e: 4c 89 f0 mov %r14,%rax
11: 48 c1 e8 03 shr $0x3,%rax
15: 42 80 3c 20 00 cmpb $0x0,(%rax,%r12,1)
1a: 74 08 je 0x24
1c: 4c 89 f7 mov %r14,%rdi
1f: e8 2f de e6 fc call 0xfce6de53
24: 41 03 1e add (%r14),%ebx
27: 89 da mov %ebx,%edx
29: ec in (%dx),%al
* 2a: 0f b6 c0 movzbl %al,%eax <-- trapping instruction
2d: 5b pop %rbx
2e: 41 5c pop %r12
30: 41 5e pop %r14
32: 41 5f pop %r15
34: e9 da 9f 72 06 jmp 0x672a013
39: cc int3
3a: 44 89 f9 mov %r15d,%ecx
3d: 80 e1 07 and $0x7,%cl
---
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
syzbot found the following issue on:
HEAD commit: 9845cf73f7db Add linux-next specific files for 20260205
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1568fa5a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=ac78ce3b6729749e
dashboard link: https://syzkaller.appspot.com/bug?extid=67eac54e93558f052003
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
CC: [ax...@kernel.dk linux...@vger.kernel.org linux-...@vger.kernel.org]
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9f30334a2431/disk-9845cf73.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0d58741a15a6/vmlinux-9845cf73.xz
kernel image: https://storage.googleapis.com/syzbot-assets/62204da1452c/bzImage-9845cf73.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+67eac5...@syzkaller.appspotmail.com
INFO: task poweroff:6675 blocked for more than 144 seconds.
Tainted: G L syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:poweroff state:D stack:23904 pid:6675 tgid:6675 ppid:5176 task_flags:0x400000 flags:0x00080000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5295 [inline]
__schedule+0x1585/0x5310 kernel/sched/core.c:6907
__schedule_loop kernel/sched/core.c:6989 [inline]
schedule+0x164/0x360 kernel/sched/core.c:7004
schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:7061
__mutex_lock_common kernel/locking/mutex.c:692 [inline]
__mutex_lock+0x7fe/0x1300 kernel/locking/mutex.c:776
sync_bdevs+0x27e/0x470 block/bdev.c:1304
ksys_sync fs/sync.c:105 [inline]
__ia32_sys_sync+0xc5/0x120 fs/sync.c:111
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x14d/0xf80 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fa532cc8f37
RSP: 002b:00007ffcecf9e738 EFLAGS: 00000246 ORIG_RAX: 00000000000000a2
RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007fa532cc8f37
RDX: ffffffffffffff88 RSI: 00007fa532e61e51 RDI: 00000000ffffff9c
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffcecf9e898 R14: 00007fa532eab000 R15: 00005629478cad98
</TASK>
Showing all locks held in the system:
1 lock held by khungtaskd/30:
#0: ffffffff8e960320 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:312 [inline]
#0: ffffffff8e960320 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:850 [inline]
#0: ffffffff8e960320 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x2e/0x180 kernel/locking/lockdep.c:6775
6 locks held by kworker/0:2/796:
#0: ffff888021abb948 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x855/0x1650 kernel/workqueue.c:3254
#1: ffffc90003367c40 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x87c/0x1650 kernel/workqueue.c:3255
#2: ffff888029f45198 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:895 [inline]
#2: ffff888029f45198 (&dev->mutex){....}-{4:4}, at: hub_event+0x17f/0x4f30 drivers/usb/core/hub.c:5899
#3: ffff888029f42518 (&port_dev->status_lock){+.+.}-{4:4}, at: usb_lock_port drivers/usb/core/hub.c:3252 [inline]
#3: ffff888029f42518 (&port_dev->status_lock){+.+.}-{4:4}, at: hub_port_connect drivers/usb/core/hub.c:5464 [inline]
#3: ffff888029f42518 (&port_dev->status_lock){+.+.}-{4:4}, at: hub_port_connect_change drivers/usb/core/hub.c:5707 [inline]
#3: ffff888029f42518 (&port_dev->status_lock){+.+.}-{4:4}, at: port_event drivers/usb/core/hub.c:5871 [inline]
#3: ffff888029f42518 (&port_dev->status_lock){+.+.}-{4:4}, at: hub_event+0x217a/0x4f30 drivers/usb/core/hub.c:5953
#4: ffff888029ec1c68 (hcd->address0_mutex){+.+.}-{4:4}, at: hub_port_connect drivers/usb/core/hub.c:5465 [inline]
#4: ffff888029ec1c68 (hcd->address0_mutex){+.+.}-{4:4}, at: hub_port_connect_change drivers/usb/core/hub.c:5707 [inline]
#4: ffff888029ec1c68 (hcd->address0_mutex){+.+.}-{4:4}, at: port_event drivers/usb/core/hub.c:5871 [inline]
#4: ffff888029ec1c68 (hcd->address0_mutex){+.+.}-{4:4}, at: hub_event+0x21a2/0x4f30 drivers/usb/core/hub.c:5953
#5: ffffffff8f68ef30 (ehci_cf_port_reset_rwsem){.+.+}-{4:4}, at: hub_port_reset+0x14e/0x1840 drivers/usb/core/hub.c:3067
5 locks held by kworker/u8:7/3482:
2 locks held by getty/5581:
#0: ffff88803214d0a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
#1: ffffc9000332b2f0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x45c/0x13c0 drivers/tty/n_tty.c:2211
1 lock held by udevd/5833:
#0: ffff888026cbd358 (&disk->open_mutex){+.+.}-{4:4}, at: bdev_open+0xe0/0xd30 block/bdev.c:961
2 locks held by kworker/0:4/5873:
1 lock held by poweroff/6675:
#0: ffff888026cbd358 (&disk->open_mutex){+.+.}-{4:4}, at: sync_bdevs+0x27e/0x470 block/bdev.c:1304
=============================================
NMI backtrace for cpu 1
CPU: 1 UID: 0 PID: 30 Comm: khungtaskd Tainted: G L syzkaller #0 PREEMPT(full)
Tainted: [L]=SOFTLOCKUP
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/24/2026
Call Trace:
<TASK>
dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
nmi_cpu_backtrace+0x274/0x2d0 lib/nmi_backtrace.c:113
nmi_trigger_cpumask_backtrace+0x17a/0x300 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:161 [inline]
__sys_info lib/sys_info.c:157 [inline]
sys_info+0x135/0x170 lib/sys_info.c:165
check_hung_uninterruptible_tasks kernel/hung_task.c:347 [inline]
watchdog+0x103d/0x1090 kernel/hung_task.c:516
kthread+0x388/0x470 kernel/kthread.c:467
ret_from_fork+0x51e/0xb90 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 796 Comm: kworker/0:2 Tainted: G L syzkaller #0 PREEMPT(full)
Tainted: [L]=SOFTLOCKUP
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/24/2026
Workqueue: usb_hub_wq hub_event
RIP: 0010:io_serial_in+0x77/0xc0 drivers/tty/serial/8250/8250_port.c:400
Code: e8 be f4 7c fc 44 89 f9 d3 e3 49 83 c6 40 4c 89 f0 48 c1 e8 03 42 80 3c 20 00 74 08 4c 89 f7 e8 2f de e6 fc 41 03 1e 89 da ec <0f> b6 c0 5b 41 5c 41 5e 41 5f e9 da 9f 72 06 cc 44 89 f9 80 e1 07
RSP: 0018:ffffc90003367070 EFLAGS: 00000002
RAX: 1ffffffff3503100 RBX: 00000000000003fd RCX: 0000000000000000
RDX: 00000000000003fd RSI: 000000000000f581 RDI: 000000000000f582
RBP: ffffffff9a818ed0 R08: ffff888025aa8237 R09: 1ffff11004b55046
R10: dffffc0000000000 R11: ffffffff8548f8c0 R12: dffffc0000000000
R13: 0000000000000000 R14: ffffffff9a818c40 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff888125015000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005555753eba28 CR3: 0000000078912000 CR4: 00000000003526f0
Call Trace:
<TASK>
serial_in drivers/tty/serial/8250/8250.h:128 [inline]
serial_lsr_in drivers/tty/serial/8250/8250.h:150 [inline]
wait_for_lsr+0x1a1/0x2f0 drivers/tty/serial/8250/8250_port.c:1961
fifo_wait_for_lsr drivers/tty/serial/8250/8250_port.c:3234 [inline]
serial8250_console_fifo_write drivers/tty/serial/8250/8250_port.c:3257 [inline]
serial8250_console_write+0x1348/0x1ba0 drivers/tty/serial/8250/8250_port.c:3342
console_emit_next_record kernel/printk/printk.c:3131 [inline]
console_flush_one_record kernel/printk/printk.c:3217 [inline]
console_flush_all+0x718/0xb20 kernel/printk/printk.c:3291
__console_flush_and_unlock kernel/printk/printk.c:3321 [inline]
console_unlock+0xd1/0x1c0 kernel/printk/printk.c:3361
vprintk_emit+0x485/0x560 kernel/printk/printk.c:2428
dev_vprintk_emit+0x355/0x420 drivers/base/core.c:4914
dev_printk_emit+0xee/0x140 drivers/base/core.c:4925
_dev_info+0x11e/0x180 drivers/base/core.c:4983
hub_port_connect drivers/usb/core/hub.c:5606 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5707 [inline]
port_event drivers/usb/core/hub.c:5871 [inline]
hub_event+0x2d3a/0x4f30 drivers/usb/core/hub.c:5953
process_one_work+0x949/0x1650 kernel/workqueue.c:3279
process_scheduled_works kernel/workqueue.c:3362 [inline]
worker_thread+0xb46/0x1140 kernel/workqueue.c:3443
kthread+0x388/0x470 kernel/kthread.c:467
ret_from_fork+0x51e/0xb90 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</TASK>
----------------
Code disassembly (best guess):
0: e8 be f4 7c fc call 0xfc7cf4c3
5: 44 89 f9 mov %r15d,%ecx
8: d3 e3 shl %cl,%ebx
a: 49 83 c6 40 add $0x40,%r14
e: 4c 89 f0 mov %r14,%rax
11: 48 c1 e8 03 shr $0x3,%rax
15: 42 80 3c 20 00 cmpb $0x0,(%rax,%r12,1)
1a: 74 08 je 0x24
1c: 4c 89 f7 mov %r14,%rdi
1f: e8 2f de e6 fc call 0xfce6de53
24: 41 03 1e add (%r14),%ebx
27: 89 da mov %ebx,%edx
29: ec in (%dx),%al
* 2a: 0f b6 c0 movzbl %al,%eax <-- trapping instruction
2d: 5b pop %rbx
2e: 41 5c pop %r12
30: 41 5e pop %r14
32: 41 5f pop %r15
34: e9 da 9f 72 06 jmp 0x672a013
39: cc int3
3a: 44 89 f9 mov %r15d,%ecx
3d: 80 e1 07 and $0x7,%cl
---
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
Reply all
Reply to author
Forward
0 new messages