INFO: task hung in usbdev_open (2)

5 views
Skip to first unread message

syzbot

unread,
Nov 13, 2021, 10:46:28 PM11/13/21
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=176d0676b00000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=aeb1d8d01e24f20b550f
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+aeb1d8...@syzkaller.appspotmail.com

ieee802154 phy0 wpan0: encryption failed: -22
ieee802154 phy1 wpan1: encryption failed: -22
ieee802154 phy0 wpan0: encryption failed: -22
ieee802154 phy1 wpan1: encryption failed: -22
Bluetooth: hci2: command 0x0406 tx timeout
INFO: task syz-executor.4:27342 blocked for more than 140 seconds.
Not tainted 4.19.211-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor.4 D27376 27342 25069 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:1016 [inline]
__mutex_lock+0x5f0/0x1190 kernel/locking/mutex.c:1078
device_lock include/linux/device.h:1174 [inline]
usbdev_open+0x152/0x7f0 drivers/usb/core/devio.c:1007
chrdev_open+0x266/0x770 fs/char_dev.c:423
do_dentry_open+0x4aa/0x1160 fs/open.c:796
do_last fs/namei.c:3421 [inline]
path_openat+0x793/0x2df0 fs/namei.c:3537
do_filp_open+0x18c/0x3f0 fs/namei.c:3567
do_sys_open+0x3b3/0x520 fs/open.c:1085
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f1f2ec4ca04
Code: Bad RIP value.
RSP: 002b:00007f1f2c20ecc0 EFLAGS: 00000293 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 6666666666666667 RCX: 00007f1f2ec4ca04
RDX: 0000000000000001 RSI: 00007f1f2c20ed60 RDI: 00000000ffffff9c
RBP: 00007f1f2c20ed60 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000001
R13: 00007ffea1d8e79f R14: 00007f1f2c20f300 R15: 0000000000022000
INFO: task syz-executor.4:27344 blocked for more than 140 seconds.
Not tainted 4.19.211-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor.4 D28312 27344 25069 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:1016 [inline]
__mutex_lock+0x5f0/0x1190 kernel/locking/mutex.c:1078
device_lock include/linux/device.h:1174 [inline]
usbdev_open+0x152/0x7f0 drivers/usb/core/devio.c:1007
chrdev_open+0x266/0x770 fs/char_dev.c:423
do_dentry_open+0x4aa/0x1160 fs/open.c:796
do_last fs/namei.c:3421 [inline]
path_openat+0x793/0x2df0 fs/namei.c:3537
do_filp_open+0x18c/0x3f0 fs/namei.c:3567
do_sys_open+0x3b3/0x520 fs/open.c:1085
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f1f2ec4ca04
Code: Bad RIP value.
RSP: 002b:00007f1f2c1edcc0 EFLAGS: 00000293 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 6666666666666667 RCX: 00007f1f2ec4ca04
RDX: 0000000000000001 RSI: 00007f1f2c1edd60 RDI: 00000000ffffff9c
RBP: 00007f1f2c1edd60 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000001
R13: 00007ffea1d8e79f R14: 00007f1f2c1ee300 R15: 0000000000022000

Showing all locks held in the system:
1 lock held by khungtaskd/1570:
#0: 00000000bf4e89ed (rcu_read_lock){....}, at: debug_show_all_locks+0x53/0x265 kernel/locking/lockdep.c:4441
5 locks held by kworker/0:3/4715:
#0: 000000009cebf5c4 ((wq_completion)"usb_hub_wq"){+.+.}, at: process_one_work+0x767/0x1570 kernel/workqueue.c:2124
#1: 000000006f688bf6 ((work_completion)(&hub->events)){+.+.}, at: process_one_work+0x79c/0x1570 kernel/workqueue.c:2128
#2: 00000000ecb93b58 (&dev->mutex){....}, at: device_lock include/linux/device.h:1174 [inline]
#2: 00000000ecb93b58 (&dev->mutex){....}, at: hub_event+0x11e/0x44a0 drivers/usb/core/hub.c:5387
#3: 0000000031348649 (&port_dev->status_lock){+.+.}, at: usb_lock_port drivers/usb/core/hub.c:2983 [inline]
#3: 0000000031348649 (&port_dev->status_lock){+.+.}, at: hub_port_connect drivers/usb/core/hub.c:5069 [inline]
#3: 0000000031348649 (&port_dev->status_lock){+.+.}, at: hub_port_connect_change drivers/usb/core/hub.c:5253 [inline]
#3: 0000000031348649 (&port_dev->status_lock){+.+.}, at: port_event drivers/usb/core/hub.c:5361 [inline]
#3: 0000000031348649 (&port_dev->status_lock){+.+.}, at: hub_event+0x1cb8/0x44a0 drivers/usb/core/hub.c:5441
#4: 000000006e4e9c0a (hcd->address0_mutex){+.+.}, at: hub_port_init+0x1b9/0x3120 drivers/usb/core/hub.c:4578
1 lock held by in:imklog/7811:
#0: 0000000044f7f732 (&f->f_pos_lock){+.+.}, at: __fdget_pos+0x26f/0x310 fs/file.c:767
3 locks held by rs:main Q:Reg/7815:
1 lock held by syz-executor.4/27342:
#0: 00000000ecb93b58 (&dev->mutex){....}, at: device_lock include/linux/device.h:1174 [inline]
#0: 00000000ecb93b58 (&dev->mutex){....}, at: usbdev_open+0x152/0x7f0 drivers/usb/core/devio.c:1007
1 lock held by syz-executor.4/27344:
#0: 00000000ecb93b58 (&dev->mutex){....}, at: device_lock include/linux/device.h:1174 [inline]
#0: 00000000ecb93b58 (&dev->mutex){....}, at: usbdev_open+0x152/0x7f0 drivers/usb/core/devio.c:1007

=============================================

NMI backtrace for cpu 0
CPU: 0 PID: 1570 Comm: khungtaskd Not tainted 4.19.211-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: 4685 Comm: systemd-journal Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:__lock_release kernel/locking/lockdep.c:3714 [inline]
RIP: 0010:lock_release+0x528/0x8b0 kernel/locking/lockdep.c:3927
Code: 85 f6 75 bf 65 ff 0d 57 90 b6 7e 0f 85 49 fc ff ff e8 2e ee b4 ff e9 3f fc ff ff 48 b8 00 00 00 00 00 fc ff df 48 8b 54 24 08 <48> c1 ea 03 0f b6 04 02 84 c0 74 08 3c 03 0f 8e 16 03 00 00 45 8d
RSP: 0018:ffff8880a10df9b8 EFLAGS: 00000046
RAX: dffffc0000000000 RBX: 0000000000000003 RCX: 1ffff1101421a989
RDX: ffff8880a10d4c40 RSI: 0000000000000001 RDI: ffff8880a10d43c0
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000074071 R12: 1ffff1101421bf3a
R13: 0000000000000000 R14: ffff8880a10d43c0 R15: 0000000000000001
FS: 00007f03cec438c0(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f03cc23f000 CR3: 00000000a1728000 CR4: 00000000003426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
rcu_lock_release include/linux/rcupdate.h:247 [inline]
rcu_read_unlock include/linux/rcupdate.h:681 [inline]
is_bpf_text_address+0xfc/0x1b0 kernel/bpf/core.c:548
kernel_text_address kernel/extable.c:152 [inline]
kernel_text_address+0xbd/0xf0 kernel/extable.c:122
__kernel_text_address+0x9/0x30 kernel/extable.c:107
unwind_get_return_address arch/x86/kernel/unwind_orc.c:297 [inline]
unwind_get_return_address+0x51/0x90 arch/x86/kernel/unwind_orc.c:292
__save_stack_trace+0xaf/0x190 arch/x86/kernel/stacktrace.c:45
save_stack mm/kasan/kasan.c:448 [inline]
set_track mm/kasan/kasan.c:460 [inline]
kasan_kmalloc+0xeb/0x160 mm/kasan/kasan.c:553
slab_post_alloc_hook mm/slab.h:445 [inline]
slab_alloc mm/slab.c:3397 [inline]
kmem_cache_alloc+0x110/0x370 mm/slab.c:3557
getname_flags+0xce/0x590 fs/namei.c:140
user_path_at_empty+0x2a/0x50 fs/namei.c:2609
user_path_at include/linux/namei.h:57 [inline]
do_faccessat+0x248/0x7a0 fs/open.c:397
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f03cdefe9c7
Code: 83 c4 08 48 3d 01 f0 ff ff 73 01 c3 48 8b 0d c8 d4 2b 00 f7 d8 64 89 01 48 83 c8 ff c3 66 0f 1f 44 00 00 b8 15 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d a1 d4 2b 00 f7 d8 64 89 01 48
RSP: 002b:00007fff5d85e708 EFLAGS: 00000246 ORIG_RAX: 0000000000000015
RAX: ffffffffffffffda RBX: 00007fff5d861730 RCX: 00007f03cdefe9c7
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00005644568f49a3
RBP: 00007fff5d85e850 R08: 00005644568ea3e5 R09: 0000000000000018
R10: 0000000000000069 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 000056445839a8a0 R15: 00007fff5d85ed40
----------------
Code disassembly (best guess):
0: 85 f6 test %esi,%esi
2: 75 bf jne 0xffffffc3
4: 65 ff 0d 57 90 b6 7e decl %gs:0x7eb69057(%rip) # 0x7eb69062
b: 0f 85 49 fc ff ff jne 0xfffffc5a
11: e8 2e ee b4 ff callq 0xffb4ee44
16: e9 3f fc ff ff jmpq 0xfffffc5a
1b: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
22: fc ff df
25: 48 8b 54 24 08 mov 0x8(%rsp),%rdx
* 2a: 48 c1 ea 03 shr $0x3,%rdx <-- trapping instruction
2e: 0f b6 04 02 movzbl (%rdx,%rax,1),%eax
32: 84 c0 test %al,%al
34: 74 08 je 0x3e
36: 3c 03 cmp $0x3,%al
38: 0f 8e 16 03 00 00 jle 0x354
3e: 45 rex.RB
3f: 8d .byte 0x8d


---
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

unread,
Mar 21, 2022, 5:54:17 AM3/21/22
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages