INFO: task can't die in usbdev_open
9 views
Skip to first unread message
syzbot
Oct 11, 2020, 6:31:24 PM10/11/20
to syzkaller-upst...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 8b787da7 Add linux-next specific files for 20201007
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=12d7a1fb900000
kernel config: https://syzkaller.appspot.com/x/.config?x=aac055e9c8fbd2b8
dashboard link: https://syzkaller.appspot.com/bug?extid=b04d9fdf29442ea65a9b
compiler: gcc (GCC) 10.1.0-syz 20200507
CC: [ar...@arndb.de gre...@linuxfoundation.org jarkko....@linux.intel.com jeremy...@arm.com linux-...@vger.kernel.org linu...@vger.kernel.org]
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+b04d9f...@syzkaller.appspotmail.com
INFO: task syz-executor.5:25433 can't die for more than 143 seconds.
task:syz-executor.5 state:D stack:27280 pid:25433 ppid: 6939 flags:0x00004004
Call Trace:
context_switch kernel/sched/core.c:3773 [inline]
__schedule+0xec5/0x2200 kernel/sched/core.c:4522
schedule+0xcf/0x270 kernel/sched/core.c:4600
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:4659
__mutex_lock_common kernel/locking/mutex.c:1033 [inline]
__mutex_lock+0x3e2/0x10e0 kernel/locking/mutex.c:1103
device_lock include/linux/device.h:731 [inline]
usbdev_open+0x19d/0x930 drivers/usb/core/devio.c:1029
chrdev_open+0x266/0x770 fs/char_dev.c:414
do_dentry_open+0x4b9/0x11b0 fs/open.c:817
do_open fs/namei.c:3252 [inline]
path_openat+0x1b9a/0x2730 fs/namei.c:3369
do_filp_open+0x17e/0x3c0 fs/namei.c:3396
do_sys_openat2+0x16d/0x420 fs/open.c:1168
do_sys_open fs/open.c:1184 [inline]
__do_sys_open fs/open.c:1192 [inline]
__se_sys_open fs/open.c:1188 [inline]
__x64_sys_open+0x119/0x1c0 fs/open.c:1188
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x417921
Code: Unable to access opcode bytes at RIP 0x4178f7.
RSP: 002b:00007fd9475ca820 EFLAGS: 00000293 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 6666666666666667 RCX: 0000000000417921
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 00007fd9475ca850
RBP: 000000000118bf60 R08: 000000000000000f R09: 0000000000000000
R10: 0000000000000006 R11: 0000000000000293 R12: 000000000118bf2c
R13: 00007ffe9b95e16f R14: 00007fd9475cb9c0 R15: 000000000118bf2c
INFO: task syz-executor.5:25433 blocked for more than 143 seconds.
Not tainted 5.9.0-rc8-next-20201007-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.5 state:D stack:27280 pid:25433 ppid: 6939 flags:0x00004004
Call Trace:
context_switch kernel/sched/core.c:3773 [inline]
__schedule+0xec5/0x2200 kernel/sched/core.c:4522
schedule+0xcf/0x270 kernel/sched/core.c:4600
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:4659
__mutex_lock_common kernel/locking/mutex.c:1033 [inline]
__mutex_lock+0x3e2/0x10e0 kernel/locking/mutex.c:1103
device_lock include/linux/device.h:731 [inline]
usbdev_open+0x19d/0x930 drivers/usb/core/devio.c:1029
chrdev_open+0x266/0x770 fs/char_dev.c:414
do_dentry_open+0x4b9/0x11b0 fs/open.c:817
do_open fs/namei.c:3252 [inline]
path_openat+0x1b9a/0x2730 fs/namei.c:3369
do_filp_open+0x17e/0x3c0 fs/namei.c:3396
do_sys_openat2+0x16d/0x420 fs/open.c:1168
do_sys_open fs/open.c:1184 [inline]
__do_sys_open fs/open.c:1192 [inline]
__se_sys_open fs/open.c:1188 [inline]
__x64_sys_open+0x119/0x1c0 fs/open.c:1188
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x417921
Code: Unable to access opcode bytes at RIP 0x4178f7.
RSP: 002b:00007fd9475ca820 EFLAGS: 00000293 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 6666666666666667 RCX: 0000000000417921
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 00007fd9475ca850
RBP: 000000000118bf60 R08: 000000000000000f R09: 0000000000000000
R10: 0000000000000006 R11: 0000000000000293 R12: 000000000118bf2c
R13: 00007ffe9b95e16f R14: 00007fd9475cb9c0 R15: 000000000118bf2c
INFO: task syz-executor.5:25446 can't die for more than 144 seconds.
task:syz-executor.5 state:D stack:27064 pid:25446 ppid: 6939 flags:0x00004004
Call Trace:
context_switch kernel/sched/core.c:3773 [inline]
__schedule+0xec5/0x2200 kernel/sched/core.c:4522
schedule+0xcf/0x270 kernel/sched/core.c:4600
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:4659
__mutex_lock_common kernel/locking/mutex.c:1033 [inline]
__mutex_lock+0x3e2/0x10e0 kernel/locking/mutex.c:1103
device_lock include/linux/device.h:731 [inline]
usbdev_open+0x19d/0x930 drivers/usb/core/devio.c:1029
chrdev_open+0x266/0x770 fs/char_dev.c:414
do_dentry_open+0x4b9/0x11b0 fs/open.c:817
do_open fs/namei.c:3252 [inline]
path_openat+0x1b9a/0x2730 fs/namei.c:3369
do_filp_open+0x17e/0x3c0 fs/namei.c:3396
do_sys_openat2+0x16d/0x420 fs/open.c:1168
do_sys_open fs/open.c:1184 [inline]
__do_sys_open fs/open.c:1192 [inline]
__se_sys_open fs/open.c:1188 [inline]
__x64_sys_open+0x119/0x1c0 fs/open.c:1188
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x417921
Code: Unable to access opcode bytes at RIP 0x4178f7.
RSP: 002b:00007fd9475a9820 EFLAGS: 00000293 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 6666666666666667 RCX: 0000000000417921
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 00007fd9475a9850
RBP: 000000000118c008 R08: 000000000000000f R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000293 R12: 000000000118bfd4
R13: 00007ffe9b95e16f R14: 00007fd9475aa9c0 R15: 000000000118bfd4
INFO: task syz-executor.5:25446 blocked for more than 144 seconds.
Not tainted 5.9.0-rc8-next-20201007-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.5 state:D stack:27064 pid:25446 ppid: 6939 flags:0x00004004
Call Trace:
context_switch kernel/sched/core.c:3773 [inline]
__schedule+0xec5/0x2200 kernel/sched/core.c:4522
schedule+0xcf/0x270 kernel/sched/core.c:4600
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:4659
__mutex_lock_common kernel/locking/mutex.c:1033 [inline]
__mutex_lock+0x3e2/0x10e0 kernel/locking/mutex.c:1103
device_lock include/linux/device.h:731 [inline]
usbdev_open+0x19d/0x930 drivers/usb/core/devio.c:1029
chrdev_open+0x266/0x770 fs/char_dev.c:414
do_dentry_open+0x4b9/0x11b0 fs/open.c:817
do_open fs/namei.c:3252 [inline]
path_openat+0x1b9a/0x2730 fs/namei.c:3369
do_filp_open+0x17e/0x3c0 fs/namei.c:3396
do_sys_openat2+0x16d/0x420 fs/open.c:1168
do_sys_open fs/open.c:1184 [inline]
__do_sys_open fs/open.c:1192 [inline]
__se_sys_open fs/open.c:1188 [inline]
__x64_sys_open+0x119/0x1c0 fs/open.c:1188
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x417921
Code: Unable to access opcode bytes at RIP 0x4178f7.
RSP: 002b:00007fd9475a9820 EFLAGS: 00000293 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 6666666666666667 RCX: 0000000000417921
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 00007fd9475a9850
RBP: 000000000118c008 R08: 000000000000000f R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000293 R12: 000000000118bfd4
R13: 00007ffe9b95e16f R14: 00007fd9475aa9c0 R15: 000000000118bfd4
Showing all locks held in the system:
1 lock held by khungtaskd/1173:
#0: ffffffff8a554de0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x53/0x260 kernel/locking/lockdep.c:6242
1 lock held by in:imklog/6559:
#0: ffff888023fa2670 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0xe9/0x100 fs/file.c:930
2 locks held by agetty/6793:
#0: ffff888012657098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x22/0x80 drivers/tty/tty_ldisc.c:266
#1: ffffc90000fc42e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x223/0x1a70 drivers/tty/n_tty.c:2156
5 locks held by kworker/0:5/8973:
#0: ffff888013081138 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: arch_atomic64_set arch/x86/include/asm/atomic64_64.h:34 [inline]
#0: ffff888013081138 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: atomic64_set include/asm-generic/atomic-instrumented.h:856 [inline]
#0: ffff888013081138 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: atomic_long_set include/asm-generic/atomic-long.h:41 [inline]
#0: ffff888013081138 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:616 [inline]
#0: ffff888013081138 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:643 [inline]
#0: ffff888013081138 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x821/0x15a0 kernel/workqueue.c:2240
#1: ffffc90008ab7da8 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x854/0x15a0 kernel/workqueue.c:2244
#2: ffff888010d88218 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:731 [inline]
#2: ffff888010d88218 (&dev->mutex){....}-{3:3}, at: hub_event+0x1b6/0x3dd0 drivers/usb/core/hub.c:5536
#3: ffff88813472e588 (&port_dev->status_lock){+.+.}-{3:3}, at: usb_lock_port drivers/usb/core/hub.c:3029 [inline]
#3: ffff88813472e588 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect drivers/usb/core/hub.c:5153 [inline]
#3: ffff88813472e588 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect_change drivers/usb/core/hub.c:5362 [inline]
#3: ffff88813472e588 (&port_dev->status_lock){+.+.}-{3:3}, at: port_event drivers/usb/core/hub.c:5508 [inline]
#3: ffff88813472e588 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_event+0x1e55/0x3dd0 drivers/usb/core/hub.c:5590
#4: ffff888134703c68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_port_init+0x1b6/0x2d40 drivers/usb/core/hub.c:4581
1 lock held by syz-executor.5/25433:
#0: ffff888010d88218 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:731 [inline]
#0: ffff888010d88218 (&dev->mutex){....}-{3:3}, at: usbdev_open+0x19d/0x930 drivers/usb/core/devio.c:1029
1 lock held by syz-executor.5/25446:
#0: ffff888010d88218 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:731 [inline]
#0: ffff888010d88218 (&dev->mutex){....}-{3:3}, at: usbdev_open+0x19d/0x930 drivers/usb/core/devio.c:1029
=============================================
NMI backtrace for cpu 1
CPU: 1 PID: 1173 Comm: khungtaskd Not tainted 5.9.0-rc8-next-20201007-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+0x198/0x1fb lib/dump_stack.c:118
nmi_cpu_backtrace.cold+0x44/0xd7 lib/nmi_backtrace.c:105
nmi_trigger_cpumask_backtrace+0x1b3/0x230 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:147 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:253 [inline]
watchdog+0xd89/0xf30 kernel/hung_task.c:339
kthread+0x3af/0x4a0 kernel/kthread.c:292
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:296
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 3908 Comm: systemd-journal Not tainted 5.9.0-rc8-next-20201007-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:check_preemption_disabled+0x35/0x130 lib/smp_processor_id.c:54
Code: 89 fd 53 0f 1f 44 00 00 65 44 8b 25 d5 77 bc 77 65 8b 1d ee e0 bc 77 81 e3 ff ff ff 7f 31 ff 89 de 0f 1f 44 00 00 85 db 74 11 <0f> 1f 44 00 00 44 89 e0 5b 5d 41 5c 41 5d 41 5e c3 0f 1f 44 00 00
RSP: 0018:ffffc90000dd7cb0 EFLAGS: 00000002
RAX: 0000000000000001 RBX: 0000000000000004 RCX: ffffffff8128b121
RDX: 0000000000000001 RSI: 0000000000000004 RDI: 0000000000000000
RBP: ffffffff88f95480 R08: 0000000000000000 R09: ffffffff8bb575cf
R10: fffffbfff176aeb9 R11: 0000000000000001 R12: 0000000000000000
R13: ffffffff88f95440 R14: ffff88800fc53a80 R15: 0000000000000000
FS: 00007f610d4a98c0(0000) GS:ffff8880ae400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f610ab7f000 CR3: 0000000024da6000 CR4: 00000000001526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
---
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: 8b787da7 Add linux-next specific files for 20201007
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=12d7a1fb900000
kernel config: https://syzkaller.appspot.com/x/.config?x=aac055e9c8fbd2b8
dashboard link: https://syzkaller.appspot.com/bug?extid=b04d9fdf29442ea65a9b
compiler: gcc (GCC) 10.1.0-syz 20200507
CC: [ar...@arndb.de gre...@linuxfoundation.org jarkko....@linux.intel.com jeremy...@arm.com linux-...@vger.kernel.org linu...@vger.kernel.org]
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+b04d9f...@syzkaller.appspotmail.com
INFO: task syz-executor.5:25433 can't die for more than 143 seconds.
task:syz-executor.5 state:D stack:27280 pid:25433 ppid: 6939 flags:0x00004004
Call Trace:
context_switch kernel/sched/core.c:3773 [inline]
__schedule+0xec5/0x2200 kernel/sched/core.c:4522
schedule+0xcf/0x270 kernel/sched/core.c:4600
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:4659
__mutex_lock_common kernel/locking/mutex.c:1033 [inline]
__mutex_lock+0x3e2/0x10e0 kernel/locking/mutex.c:1103
device_lock include/linux/device.h:731 [inline]
usbdev_open+0x19d/0x930 drivers/usb/core/devio.c:1029
chrdev_open+0x266/0x770 fs/char_dev.c:414
do_dentry_open+0x4b9/0x11b0 fs/open.c:817
do_open fs/namei.c:3252 [inline]
path_openat+0x1b9a/0x2730 fs/namei.c:3369
do_filp_open+0x17e/0x3c0 fs/namei.c:3396
do_sys_openat2+0x16d/0x420 fs/open.c:1168
do_sys_open fs/open.c:1184 [inline]
__do_sys_open fs/open.c:1192 [inline]
__se_sys_open fs/open.c:1188 [inline]
__x64_sys_open+0x119/0x1c0 fs/open.c:1188
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x417921
Code: Unable to access opcode bytes at RIP 0x4178f7.
RSP: 002b:00007fd9475ca820 EFLAGS: 00000293 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 6666666666666667 RCX: 0000000000417921
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 00007fd9475ca850
RBP: 000000000118bf60 R08: 000000000000000f R09: 0000000000000000
R10: 0000000000000006 R11: 0000000000000293 R12: 000000000118bf2c
R13: 00007ffe9b95e16f R14: 00007fd9475cb9c0 R15: 000000000118bf2c
INFO: task syz-executor.5:25433 blocked for more than 143 seconds.
Not tainted 5.9.0-rc8-next-20201007-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.5 state:D stack:27280 pid:25433 ppid: 6939 flags:0x00004004
Call Trace:
context_switch kernel/sched/core.c:3773 [inline]
__schedule+0xec5/0x2200 kernel/sched/core.c:4522
schedule+0xcf/0x270 kernel/sched/core.c:4600
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:4659
__mutex_lock_common kernel/locking/mutex.c:1033 [inline]
__mutex_lock+0x3e2/0x10e0 kernel/locking/mutex.c:1103
device_lock include/linux/device.h:731 [inline]
usbdev_open+0x19d/0x930 drivers/usb/core/devio.c:1029
chrdev_open+0x266/0x770 fs/char_dev.c:414
do_dentry_open+0x4b9/0x11b0 fs/open.c:817
do_open fs/namei.c:3252 [inline]
path_openat+0x1b9a/0x2730 fs/namei.c:3369
do_filp_open+0x17e/0x3c0 fs/namei.c:3396
do_sys_openat2+0x16d/0x420 fs/open.c:1168
do_sys_open fs/open.c:1184 [inline]
__do_sys_open fs/open.c:1192 [inline]
__se_sys_open fs/open.c:1188 [inline]
__x64_sys_open+0x119/0x1c0 fs/open.c:1188
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x417921
Code: Unable to access opcode bytes at RIP 0x4178f7.
RSP: 002b:00007fd9475ca820 EFLAGS: 00000293 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 6666666666666667 RCX: 0000000000417921
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 00007fd9475ca850
RBP: 000000000118bf60 R08: 000000000000000f R09: 0000000000000000
R10: 0000000000000006 R11: 0000000000000293 R12: 000000000118bf2c
R13: 00007ffe9b95e16f R14: 00007fd9475cb9c0 R15: 000000000118bf2c
INFO: task syz-executor.5:25446 can't die for more than 144 seconds.
task:syz-executor.5 state:D stack:27064 pid:25446 ppid: 6939 flags:0x00004004
Call Trace:
context_switch kernel/sched/core.c:3773 [inline]
__schedule+0xec5/0x2200 kernel/sched/core.c:4522
schedule+0xcf/0x270 kernel/sched/core.c:4600
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:4659
__mutex_lock_common kernel/locking/mutex.c:1033 [inline]
__mutex_lock+0x3e2/0x10e0 kernel/locking/mutex.c:1103
device_lock include/linux/device.h:731 [inline]
usbdev_open+0x19d/0x930 drivers/usb/core/devio.c:1029
chrdev_open+0x266/0x770 fs/char_dev.c:414
do_dentry_open+0x4b9/0x11b0 fs/open.c:817
do_open fs/namei.c:3252 [inline]
path_openat+0x1b9a/0x2730 fs/namei.c:3369
do_filp_open+0x17e/0x3c0 fs/namei.c:3396
do_sys_openat2+0x16d/0x420 fs/open.c:1168
do_sys_open fs/open.c:1184 [inline]
__do_sys_open fs/open.c:1192 [inline]
__se_sys_open fs/open.c:1188 [inline]
__x64_sys_open+0x119/0x1c0 fs/open.c:1188
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x417921
Code: Unable to access opcode bytes at RIP 0x4178f7.
RSP: 002b:00007fd9475a9820 EFLAGS: 00000293 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 6666666666666667 RCX: 0000000000417921
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 00007fd9475a9850
RBP: 000000000118c008 R08: 000000000000000f R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000293 R12: 000000000118bfd4
R13: 00007ffe9b95e16f R14: 00007fd9475aa9c0 R15: 000000000118bfd4
INFO: task syz-executor.5:25446 blocked for more than 144 seconds.
Not tainted 5.9.0-rc8-next-20201007-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.5 state:D stack:27064 pid:25446 ppid: 6939 flags:0x00004004
Call Trace:
context_switch kernel/sched/core.c:3773 [inline]
__schedule+0xec5/0x2200 kernel/sched/core.c:4522
schedule+0xcf/0x270 kernel/sched/core.c:4600
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:4659
__mutex_lock_common kernel/locking/mutex.c:1033 [inline]
__mutex_lock+0x3e2/0x10e0 kernel/locking/mutex.c:1103
device_lock include/linux/device.h:731 [inline]
usbdev_open+0x19d/0x930 drivers/usb/core/devio.c:1029
chrdev_open+0x266/0x770 fs/char_dev.c:414
do_dentry_open+0x4b9/0x11b0 fs/open.c:817
do_open fs/namei.c:3252 [inline]
path_openat+0x1b9a/0x2730 fs/namei.c:3369
do_filp_open+0x17e/0x3c0 fs/namei.c:3396
do_sys_openat2+0x16d/0x420 fs/open.c:1168
do_sys_open fs/open.c:1184 [inline]
__do_sys_open fs/open.c:1192 [inline]
__se_sys_open fs/open.c:1188 [inline]
__x64_sys_open+0x119/0x1c0 fs/open.c:1188
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x417921
Code: Unable to access opcode bytes at RIP 0x4178f7.
RSP: 002b:00007fd9475a9820 EFLAGS: 00000293 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 6666666666666667 RCX: 0000000000417921
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 00007fd9475a9850
RBP: 000000000118c008 R08: 000000000000000f R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000293 R12: 000000000118bfd4
R13: 00007ffe9b95e16f R14: 00007fd9475aa9c0 R15: 000000000118bfd4
Showing all locks held in the system:
1 lock held by khungtaskd/1173:
#0: ffffffff8a554de0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x53/0x260 kernel/locking/lockdep.c:6242
1 lock held by in:imklog/6559:
#0: ffff888023fa2670 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0xe9/0x100 fs/file.c:930
2 locks held by agetty/6793:
#0: ffff888012657098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x22/0x80 drivers/tty/tty_ldisc.c:266
#1: ffffc90000fc42e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x223/0x1a70 drivers/tty/n_tty.c:2156
5 locks held by kworker/0:5/8973:
#0: ffff888013081138 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: arch_atomic64_set arch/x86/include/asm/atomic64_64.h:34 [inline]
#0: ffff888013081138 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: atomic64_set include/asm-generic/atomic-instrumented.h:856 [inline]
#0: ffff888013081138 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: atomic_long_set include/asm-generic/atomic-long.h:41 [inline]
#0: ffff888013081138 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:616 [inline]
#0: ffff888013081138 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:643 [inline]
#0: ffff888013081138 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x821/0x15a0 kernel/workqueue.c:2240
#1: ffffc90008ab7da8 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x854/0x15a0 kernel/workqueue.c:2244
#2: ffff888010d88218 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:731 [inline]
#2: ffff888010d88218 (&dev->mutex){....}-{3:3}, at: hub_event+0x1b6/0x3dd0 drivers/usb/core/hub.c:5536
#3: ffff88813472e588 (&port_dev->status_lock){+.+.}-{3:3}, at: usb_lock_port drivers/usb/core/hub.c:3029 [inline]
#3: ffff88813472e588 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect drivers/usb/core/hub.c:5153 [inline]
#3: ffff88813472e588 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect_change drivers/usb/core/hub.c:5362 [inline]
#3: ffff88813472e588 (&port_dev->status_lock){+.+.}-{3:3}, at: port_event drivers/usb/core/hub.c:5508 [inline]
#3: ffff88813472e588 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_event+0x1e55/0x3dd0 drivers/usb/core/hub.c:5590
#4: ffff888134703c68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_port_init+0x1b6/0x2d40 drivers/usb/core/hub.c:4581
1 lock held by syz-executor.5/25433:
#0: ffff888010d88218 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:731 [inline]
#0: ffff888010d88218 (&dev->mutex){....}-{3:3}, at: usbdev_open+0x19d/0x930 drivers/usb/core/devio.c:1029
1 lock held by syz-executor.5/25446:
#0: ffff888010d88218 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:731 [inline]
#0: ffff888010d88218 (&dev->mutex){....}-{3:3}, at: usbdev_open+0x19d/0x930 drivers/usb/core/devio.c:1029
=============================================
NMI backtrace for cpu 1
CPU: 1 PID: 1173 Comm: khungtaskd Not tainted 5.9.0-rc8-next-20201007-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+0x198/0x1fb lib/dump_stack.c:118
nmi_cpu_backtrace.cold+0x44/0xd7 lib/nmi_backtrace.c:105
nmi_trigger_cpumask_backtrace+0x1b3/0x230 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:147 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:253 [inline]
watchdog+0xd89/0xf30 kernel/hung_task.c:339
kthread+0x3af/0x4a0 kernel/kthread.c:292
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:296
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 3908 Comm: systemd-journal Not tainted 5.9.0-rc8-next-20201007-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:check_preemption_disabled+0x35/0x130 lib/smp_processor_id.c:54
Code: 89 fd 53 0f 1f 44 00 00 65 44 8b 25 d5 77 bc 77 65 8b 1d ee e0 bc 77 81 e3 ff ff ff 7f 31 ff 89 de 0f 1f 44 00 00 85 db 74 11 <0f> 1f 44 00 00 44 89 e0 5b 5d 41 5c 41 5d 41 5e c3 0f 1f 44 00 00
RSP: 0018:ffffc90000dd7cb0 EFLAGS: 00000002
RAX: 0000000000000001 RBX: 0000000000000004 RCX: ffffffff8128b121
RDX: 0000000000000001 RSI: 0000000000000004 RDI: 0000000000000000
RBP: ffffffff88f95480 R08: 0000000000000000 R09: ffffffff8bb575cf
R10: fffffbfff176aeb9 R11: 0000000000000001 R12: 0000000000000000
R13: ffffffff88f95440 R14: ffff88800fc53a80 R15: 0000000000000000
FS: 00007f610d4a98c0(0000) GS:ffff8880ae400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f610ab7f000 CR3: 0000000024da6000 CR4: 00000000001526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
---
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
Apr 2, 2021, 2:49:20 PM4/2/21
to syzkaller-upst...@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