INFO: task hung in hub_activate
17 views
Skip to first unread message
syzbot
Aug 17, 2021, 7:39:23 AM8/17/21
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 59456c9cc40c Linux 4.19.204
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10161461300000
kernel config: https://syzkaller.appspot.com/x/.config?x=a84b4514346e13dc
dashboard link: https://syzkaller.appspot.com/bug?extid=c3017f57b80a9c7810a8
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+c3017f...@syzkaller.appspotmail.com
block nbd5: shutting down sockets
ieee802154 phy0 wpan0: encryption failed: -22
ieee802154 phy1 wpan1: encryption failed: -22
ieee802154 phy0 wpan0: encryption failed: -22
ieee802154 phy1 wpan1: encryption failed: -22
INFO: task kworker/1:1:25896 blocked for more than 140 seconds.
Not tainted 4.19.204-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kworker/1:1 D28168 25896 2 0x80000000
Workqueue: events_power_efficient hub_init_func3
Call Trace:
context_switch kernel/sched/core.c:2828 [inline]
__schedule+0x887/0x2040 kernel/sched/core.c:3517
schedule+0x8d/0x1b0 kernel/sched/core.c:3561
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:3619
__mutex_lock_common kernel/locking/mutex.c:1015 [inline]
__mutex_lock+0x604/0x1200 kernel/locking/mutex.c:1083
device_lock include/linux/device.h:1173 [inline]
hub_activate+0xe7a/0x1a40 drivers/usb/core/hub.c:1008
process_one_work+0x864/0x1570 kernel/workqueue.c:2153
worker_thread+0x64c/0x1130 kernel/workqueue.c:2296
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
INFO: task syz-executor.5:7095 blocked for more than 140 seconds.
Not tainted 4.19.204-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor.5 D26704 7095 8116 0x00000004
Call Trace:
context_switch kernel/sched/core.c:2828 [inline]
__schedule+0x887/0x2040 kernel/sched/core.c:3517
schedule+0x8d/0x1b0 kernel/sched/core.c:3561
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:3619
__mutex_lock_common kernel/locking/mutex.c:1015 [inline]
__mutex_lock+0x604/0x1200 kernel/locking/mutex.c:1083
device_lock include/linux/device.h:1173 [inline]
usbdev_do_ioctl+0x193/0x3030 drivers/usb/core/devio.c:2393
usbdev_ioctl+0x21/0x30 drivers/usb/core/devio.c:2585
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:501 [inline]
do_vfs_ioctl+0xcdb/0x12e0 fs/ioctl.c:688
ksys_ioctl+0x9b/0xc0 fs/ioctl.c:705
__do_sys_ioctl fs/ioctl.c:712 [inline]
__se_sys_ioctl fs/ioctl.c:710 [inline]
__x64_sys_ioctl+0x6f/0xb0 fs/ioctl.c:710
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x4665e9
Code: Bad RIP value.
RSP: 002b:00007f15b5c68188 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 000000000056bf80 RCX: 00000000004665e9
RDX: 0000000020000380 RSI: 000000008108551b RDI: 0000000000000003
RBP: 00000000004bfcc4 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000056bf80
R13: 00007fff60e1045f R14: 00007f15b5c68300 R15: 0000000000022000
Showing all locks held in the system:
1 lock held by khungtaskd/1570:
#0: 000000002c719f21 (rcu_read_lock){....}, at: debug_show_all_locks+0x53/0x265 kernel/locking/lockdep.c:4441
2 locks held by kworker/u4:4/3593:
#0: 000000003f614447 (&rq->lock){-.-.}, at: idle_balance kernel/sched/fair.c:9702 [inline]
#0: 000000003f614447 (&rq->lock){-.-.}, at: pick_next_task_fair+0x556/0x1570 kernel/sched/fair.c:6841
#1: 000000002c719f21 (rcu_read_lock){....}, at: cpu_of kernel/sched/sched.h:921 [inline]
#1: 000000002c719f21 (rcu_read_lock){....}, at: __update_idle_core+0x39/0x3e0 kernel/sched/fair.c:6057
1 lock held by in:imklog/7960:
#0: 00000000dd4a2c04 (&f->f_pos_lock){+.+.}, at: __fdget_pos+0x26f/0x310 fs/file.c:767
3 locks held by kworker/1:1/25896:
#0: 00000000725aabb9 ((wq_completion)"events_power_efficient"){+.+.}, at: process_one_work+0x767/0x1570 kernel/workqueue.c:2124
#1: 000000008e06480a ((work_completion)(&(&hub->init_work)->work)#2){+.+.}, at: process_one_work+0x79c/0x1570 kernel/workqueue.c:2128
#2: 00000000065b2b19 (&dev->mutex){....}, at: device_lock include/linux/device.h:1173 [inline]
#2: 00000000065b2b19 (&dev->mutex){....}, at: hub_activate+0xe7a/0x1a40 drivers/usb/core/hub.c:1008
5 locks held by kworker/1:2/6124:
#0: 00000000dbac20dc ((wq_completion)"usb_hub_wq"){+.+.}, at: process_one_work+0x767/0x1570 kernel/workqueue.c:2124
#1: 00000000fec50825 ((work_completion)(&hub->events)){+.+.}, at: process_one_work+0x79c/0x1570 kernel/workqueue.c:2128
#2: 00000000065b2b19 (&dev->mutex){....}, at: device_lock include/linux/device.h:1173 [inline]
#2: 00000000065b2b19 (&dev->mutex){....}, at: hub_event+0x11e/0x44a0 drivers/usb/core/hub.c:5387
#3: 00000000fce89429 (&port_dev->status_lock){+.+.}, at: usb_lock_port drivers/usb/core/hub.c:2983 [inline]
#3: 00000000fce89429 (&port_dev->status_lock){+.+.}, at: hub_port_connect drivers/usb/core/hub.c:5069 [inline]
#3: 00000000fce89429 (&port_dev->status_lock){+.+.}, at: hub_port_connect_change drivers/usb/core/hub.c:5253 [inline]
#3: 00000000fce89429 (&port_dev->status_lock){+.+.}, at: port_event drivers/usb/core/hub.c:5361 [inline]
#3: 00000000fce89429 (&port_dev->status_lock){+.+.}, at: hub_event+0x1cb8/0x44a0 drivers/usb/core/hub.c:5441
#4: 000000009c58deea (hcd->address0_mutex){+.+.}, at: hub_port_init+0x1b9/0x3120 drivers/usb/core/hub.c:4578
1 lock held by syz-executor.5/7095:
#0: 00000000065b2b19 (&dev->mutex){....}, at: device_lock include/linux/device.h:1173 [inline]
#0: 00000000065b2b19 (&dev->mutex){....}, at: usbdev_do_ioctl+0x193/0x3030 drivers/usb/core/devio.c:2393
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 1570 Comm: khungtaskd Not tainted 4.19.204-syzkaller #0
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+0x1fc/0x2ef lib/dump_stack.c:118
nmi_cpu_backtrace.cold+0x63/0xa2 lib/nmi_backtrace.c:101
nmi_trigger_cpumask_backtrace+0x1a6/0x1f0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:146 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:203 [inline]
watchdog+0x991/0xe60 kernel/hung_task.c:287
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 4690 Comm: systemd-journal Not tainted 4.19.204-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0033:0x7fb77aaaec0f
Code: 1f 40 00 48 8b 4c 24 08 4c 89 e0 48 83 ed 01 49 01 cc eb 8f 0f 1f 80 00 00 00 00 48 89 ea 4c 89 e6 4c 89 ff 48 0f af 54 24 08 <e8> 7c f2 04 00 eb 9f 4c 8b 64 24 20 48 85 ed 74 90 48 85 db 74 8b
RSP: 002b:00007ffef3a10de0 EFLAGS: 00000202
RAX: 00007ffef3a11090 RBX: 0000000000000000 RCX: 0000000000000010
RDX: 0000000000000010 RSI: 00007ffef3a11070 RDI: 00007ffef3a10f40
RBP: 0000000000000001 R08: 0000000000000010 R09: 00007ffef3a10f40
R10: 00007ffef3a11160 R11: 00007fb77abe4060 R12: 00007ffef3a11070
R13: 00007fb77b586ee0 R14: 00007ffef3a11090 R15: 00007ffef3a10f40
FS: 00007fb77b89a8c0 GS: 0000000000000000
----------------
Code disassembly (best guess), 1 bytes skipped:
0: 40 00 48 8b add %cl,-0x75(%rax)
4: 4c 24 08 rex.WR and $0x8,%al
7: 4c 89 e0 mov %r12,%rax
a: 48 83 ed 01 sub $0x1,%rbp
e: 49 01 cc add %rcx,%r12
11: eb 8f jmp 0xffffffa2
13: 0f 1f 80 00 00 00 00 nopl 0x0(%rax)
1a: 48 89 ea mov %rbp,%rdx
1d: 4c 89 e6 mov %r12,%rsi
20: 4c 89 ff mov %r15,%rdi
23: 48 0f af 54 24 08 imul 0x8(%rsp),%rdx
29: e8 7c f2 04 00 callq 0x4f2aa <-- trapping instruction
2e: eb 9f jmp 0xffffffcf
30: 4c 8b 64 24 20 mov 0x20(%rsp),%r12
35: 48 85 ed test %rbp,%rbp
38: 74 90 je 0xffffffca
3a: 48 85 db test %rbx,%rbx
3d: 74 8b je 0xffffffca
---
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.
syzbot found the following issue on:
HEAD commit: 59456c9cc40c Linux 4.19.204
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10161461300000
kernel config: https://syzkaller.appspot.com/x/.config?x=a84b4514346e13dc
dashboard link: https://syzkaller.appspot.com/bug?extid=c3017f57b80a9c7810a8
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+c3017f...@syzkaller.appspotmail.com
block nbd5: shutting down sockets
ieee802154 phy0 wpan0: encryption failed: -22
ieee802154 phy1 wpan1: encryption failed: -22
ieee802154 phy0 wpan0: encryption failed: -22
ieee802154 phy1 wpan1: encryption failed: -22
INFO: task kworker/1:1:25896 blocked for more than 140 seconds.
Not tainted 4.19.204-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kworker/1:1 D28168 25896 2 0x80000000
Workqueue: events_power_efficient hub_init_func3
Call Trace:
context_switch kernel/sched/core.c:2828 [inline]
__schedule+0x887/0x2040 kernel/sched/core.c:3517
schedule+0x8d/0x1b0 kernel/sched/core.c:3561
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:3619
__mutex_lock_common kernel/locking/mutex.c:1015 [inline]
__mutex_lock+0x604/0x1200 kernel/locking/mutex.c:1083
device_lock include/linux/device.h:1173 [inline]
hub_activate+0xe7a/0x1a40 drivers/usb/core/hub.c:1008
process_one_work+0x864/0x1570 kernel/workqueue.c:2153
worker_thread+0x64c/0x1130 kernel/workqueue.c:2296
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
INFO: task syz-executor.5:7095 blocked for more than 140 seconds.
Not tainted 4.19.204-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor.5 D26704 7095 8116 0x00000004
Call Trace:
context_switch kernel/sched/core.c:2828 [inline]
__schedule+0x887/0x2040 kernel/sched/core.c:3517
schedule+0x8d/0x1b0 kernel/sched/core.c:3561
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:3619
__mutex_lock_common kernel/locking/mutex.c:1015 [inline]
__mutex_lock+0x604/0x1200 kernel/locking/mutex.c:1083
device_lock include/linux/device.h:1173 [inline]
usbdev_do_ioctl+0x193/0x3030 drivers/usb/core/devio.c:2393
usbdev_ioctl+0x21/0x30 drivers/usb/core/devio.c:2585
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:501 [inline]
do_vfs_ioctl+0xcdb/0x12e0 fs/ioctl.c:688
ksys_ioctl+0x9b/0xc0 fs/ioctl.c:705
__do_sys_ioctl fs/ioctl.c:712 [inline]
__se_sys_ioctl fs/ioctl.c:710 [inline]
__x64_sys_ioctl+0x6f/0xb0 fs/ioctl.c:710
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x4665e9
Code: Bad RIP value.
RSP: 002b:00007f15b5c68188 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 000000000056bf80 RCX: 00000000004665e9
RDX: 0000000020000380 RSI: 000000008108551b RDI: 0000000000000003
RBP: 00000000004bfcc4 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000056bf80
R13: 00007fff60e1045f R14: 00007f15b5c68300 R15: 0000000000022000
Showing all locks held in the system:
1 lock held by khungtaskd/1570:
#0: 000000002c719f21 (rcu_read_lock){....}, at: debug_show_all_locks+0x53/0x265 kernel/locking/lockdep.c:4441
2 locks held by kworker/u4:4/3593:
#0: 000000003f614447 (&rq->lock){-.-.}, at: idle_balance kernel/sched/fair.c:9702 [inline]
#0: 000000003f614447 (&rq->lock){-.-.}, at: pick_next_task_fair+0x556/0x1570 kernel/sched/fair.c:6841
#1: 000000002c719f21 (rcu_read_lock){....}, at: cpu_of kernel/sched/sched.h:921 [inline]
#1: 000000002c719f21 (rcu_read_lock){....}, at: __update_idle_core+0x39/0x3e0 kernel/sched/fair.c:6057
1 lock held by in:imklog/7960:
#0: 00000000dd4a2c04 (&f->f_pos_lock){+.+.}, at: __fdget_pos+0x26f/0x310 fs/file.c:767
3 locks held by kworker/1:1/25896:
#0: 00000000725aabb9 ((wq_completion)"events_power_efficient"){+.+.}, at: process_one_work+0x767/0x1570 kernel/workqueue.c:2124
#1: 000000008e06480a ((work_completion)(&(&hub->init_work)->work)#2){+.+.}, at: process_one_work+0x79c/0x1570 kernel/workqueue.c:2128
#2: 00000000065b2b19 (&dev->mutex){....}, at: device_lock include/linux/device.h:1173 [inline]
#2: 00000000065b2b19 (&dev->mutex){....}, at: hub_activate+0xe7a/0x1a40 drivers/usb/core/hub.c:1008
5 locks held by kworker/1:2/6124:
#0: 00000000dbac20dc ((wq_completion)"usb_hub_wq"){+.+.}, at: process_one_work+0x767/0x1570 kernel/workqueue.c:2124
#1: 00000000fec50825 ((work_completion)(&hub->events)){+.+.}, at: process_one_work+0x79c/0x1570 kernel/workqueue.c:2128
#2: 00000000065b2b19 (&dev->mutex){....}, at: device_lock include/linux/device.h:1173 [inline]
#2: 00000000065b2b19 (&dev->mutex){....}, at: hub_event+0x11e/0x44a0 drivers/usb/core/hub.c:5387
#3: 00000000fce89429 (&port_dev->status_lock){+.+.}, at: usb_lock_port drivers/usb/core/hub.c:2983 [inline]
#3: 00000000fce89429 (&port_dev->status_lock){+.+.}, at: hub_port_connect drivers/usb/core/hub.c:5069 [inline]
#3: 00000000fce89429 (&port_dev->status_lock){+.+.}, at: hub_port_connect_change drivers/usb/core/hub.c:5253 [inline]
#3: 00000000fce89429 (&port_dev->status_lock){+.+.}, at: port_event drivers/usb/core/hub.c:5361 [inline]
#3: 00000000fce89429 (&port_dev->status_lock){+.+.}, at: hub_event+0x1cb8/0x44a0 drivers/usb/core/hub.c:5441
#4: 000000009c58deea (hcd->address0_mutex){+.+.}, at: hub_port_init+0x1b9/0x3120 drivers/usb/core/hub.c:4578
1 lock held by syz-executor.5/7095:
#0: 00000000065b2b19 (&dev->mutex){....}, at: device_lock include/linux/device.h:1173 [inline]
#0: 00000000065b2b19 (&dev->mutex){....}, at: usbdev_do_ioctl+0x193/0x3030 drivers/usb/core/devio.c:2393
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 1570 Comm: khungtaskd Not tainted 4.19.204-syzkaller #0
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+0x1fc/0x2ef lib/dump_stack.c:118
nmi_cpu_backtrace.cold+0x63/0xa2 lib/nmi_backtrace.c:101
nmi_trigger_cpumask_backtrace+0x1a6/0x1f0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:146 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:203 [inline]
watchdog+0x991/0xe60 kernel/hung_task.c:287
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 4690 Comm: systemd-journal Not tainted 4.19.204-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0033:0x7fb77aaaec0f
Code: 1f 40 00 48 8b 4c 24 08 4c 89 e0 48 83 ed 01 49 01 cc eb 8f 0f 1f 80 00 00 00 00 48 89 ea 4c 89 e6 4c 89 ff 48 0f af 54 24 08 <e8> 7c f2 04 00 eb 9f 4c 8b 64 24 20 48 85 ed 74 90 48 85 db 74 8b
RSP: 002b:00007ffef3a10de0 EFLAGS: 00000202
RAX: 00007ffef3a11090 RBX: 0000000000000000 RCX: 0000000000000010
RDX: 0000000000000010 RSI: 00007ffef3a11070 RDI: 00007ffef3a10f40
RBP: 0000000000000001 R08: 0000000000000010 R09: 00007ffef3a10f40
R10: 00007ffef3a11160 R11: 00007fb77abe4060 R12: 00007ffef3a11070
R13: 00007fb77b586ee0 R14: 00007ffef3a11090 R15: 00007ffef3a10f40
FS: 00007fb77b89a8c0 GS: 0000000000000000
----------------
Code disassembly (best guess), 1 bytes skipped:
0: 40 00 48 8b add %cl,-0x75(%rax)
4: 4c 24 08 rex.WR and $0x8,%al
7: 4c 89 e0 mov %r12,%rax
a: 48 83 ed 01 sub $0x1,%rbp
e: 49 01 cc add %rcx,%r12
11: eb 8f jmp 0xffffffa2
13: 0f 1f 80 00 00 00 00 nopl 0x0(%rax)
1a: 48 89 ea mov %rbp,%rdx
1d: 4c 89 e6 mov %r12,%rsi
20: 4c 89 ff mov %r15,%rdi
23: 48 0f af 54 24 08 imul 0x8(%rsp),%rdx
29: e8 7c f2 04 00 callq 0x4f2aa <-- trapping instruction
2e: eb 9f jmp 0xffffffcf
30: 4c 8b 64 24 20 mov 0x20(%rsp),%r12
35: 48 85 ed test %rbp,%rbp
38: 74 90 je 0xffffffca
3a: 48 85 db test %rbx,%rbx
3d: 74 8b je 0xffffffca
---
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.
syzbot
Dec 23, 2021, 1:50:17 AM12/23/21
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages