[v6.1] INFO: task hung in lookup_slow
0 views
Skip to first unread message
syzbot
Apr 14, 2024, 1:59:26 AMApr 14
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: cd5d98c0556c Linux 6.1.86
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10c64c93180000
kernel config: https://syzkaller.appspot.com/x/.config?x=cc6a54650e83f88f
dashboard link: https://syzkaller.appspot.com/bug?extid=0e98e04ea2a9550a2596
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/35b2c3edb8aa/disk-cd5d98c0.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2a5efc7ec06c/vmlinux-cd5d98c0.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9f02d0ba73da/Image-cd5d98c0.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+0e98e0...@syzkaller.appspotmail.com
INFO: task syz-executor.1:9006 blocked for more than 143 seconds.
Not tainted 6.1.86-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.1 state:D stack:0 pid:9006 ppid:7986 flags:0x00000045
Call trace:
__switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0xee4/0x1c98 kernel/sched/core.c:6558
schedule+0xc4/0x170 kernel/sched/core.c:6634
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6693
rwsem_down_read_slowpath+0x534/0x858 kernel/locking/rwsem.c:1094
__down_read_common kernel/locking/rwsem.c:1261 [inline]
__down_read kernel/locking/rwsem.c:1274 [inline]
down_read+0xac/0x308 kernel/locking/rwsem.c:1522
inode_lock_shared include/linux/fs.h:768 [inline]
lookup_slow+0x50/0x84 fs/namei.c:1706
walk_component+0x280/0x36c fs/namei.c:1998
lookup_last fs/namei.c:2455 [inline]
path_lookupat+0x13c/0x3d0 fs/namei.c:2479
filename_lookup+0x1d4/0x4e0 fs/namei.c:2508
user_path_at_empty+0x5c/0x84 fs/namei.c:2907
user_path_at include/linux/namei.h:57 [inline]
do_mount fs/namespace.c:3391 [inline]
__do_sys_mount fs/namespace.c:3602 [inline]
__se_sys_mount fs/namespace.c:3579 [inline]
__arm64_sys_mount+0x428/0x594 fs/namespace.c:3579
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
INFO: task syz-executor.1:9009 blocked for more than 143 seconds.
Not tainted 6.1.86-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.1 state:D stack:0 pid:9009 ppid:7986 flags:0x0000000d
Call trace:
__switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0xee4/0x1c98 kernel/sched/core.c:6558
schedule+0xc4/0x170 kernel/sched/core.c:6634
rwsem_down_write_slowpath+0xc80/0x156c kernel/locking/rwsem.c:1189
__down_write_common kernel/locking/rwsem.c:1314 [inline]
__down_write kernel/locking/rwsem.c:1323 [inline]
down_write+0x84/0x88 kernel/locking/rwsem.c:1574
inode_lock include/linux/fs.h:758 [inline]
open_last_lookups fs/namei.c:3549 [inline]
path_openat+0x5ec/0x2548 fs/namei.c:3782
do_filp_open+0x1bc/0x3cc fs/namei.c:3812
do_sys_openat2+0x128/0x3d8 fs/open.c:1318
do_sys_open fs/open.c:1334 [inline]
__do_sys_openat fs/open.c:1350 [inline]
__se_sys_openat fs/open.c:1345 [inline]
__arm64_sys_openat+0x1f0/0x240 fs/open.c:1345
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
INFO: task syz-executor.1:9019 blocked for more than 143 seconds.
Not tainted 6.1.86-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.1 state:D stack:0 pid:9019 ppid:7986 flags:0x00000005
Call trace:
__switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0xee4/0x1c98 kernel/sched/core.c:6558
schedule+0xc4/0x170 kernel/sched/core.c:6634
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6693
rwsem_down_read_slowpath+0x534/0x858 kernel/locking/rwsem.c:1094
__down_read_common kernel/locking/rwsem.c:1261 [inline]
__down_read kernel/locking/rwsem.c:1274 [inline]
down_read+0xac/0x308 kernel/locking/rwsem.c:1522
inode_lock_shared include/linux/fs.h:768 [inline]
open_last_lookups fs/namei.c:3551 [inline]
path_openat+0x5dc/0x2548 fs/namei.c:3782
do_filp_open+0x1bc/0x3cc fs/namei.c:3812
do_sys_openat2+0x128/0x3d8 fs/open.c:1318
do_sys_open fs/open.c:1334 [inline]
__do_sys_openat fs/open.c:1350 [inline]
__se_sys_openat fs/open.c:1345 [inline]
__arm64_sys_openat+0x1f0/0x240 fs/open.c:1345
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffff800015a14e70 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:516
1 lock held by rcu_tasks_trace/13:
#0: ffff800015a15670 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:516
1 lock held by khungtaskd/28:
#0: ffff800015a14ca0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:349
2 locks held by kworker/u4:5/1755:
#0: ffff0001b436d198 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested kernel/sched/core.c:537 [inline]
#0: ffff0001b436d198 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock kernel/sched/sched.h:1354 [inline]
#0: ffff0001b436d198 (&rq->__lock){-.-.}-{2:2}, at: rq_lock kernel/sched/sched.h:1644 [inline]
#0: ffff0001b436d198 (&rq->__lock){-.-.}-{2:2}, at: __schedule+0x2c4/0x1c98 kernel/sched/core.c:6475
#1: ffff0001b4359b88 (&per_cpu_ptr(group->pcpu, cpu)->seq){-.-.}-{0:0}, at: psi_task_switch+0x3c0/0x618 kernel/sched/psi.c:1000
2 locks held by getty/3985:
#0: ffff0000d8380098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
#1: ffff80001bce02f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1214 drivers/tty/n_tty.c:2188
3 locks held by kworker/1:6/4291:
#0: ffff0000c0020938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x664/0x1404 kernel/workqueue.c:2265
#1: ffff80001e557c20 ((work_completion)(&fw_work->work)){+.+.}-{0:0}, at: process_one_work+0x6a8/0x1404 kernel/workqueue.c:2267
#2: ffff8000158c4510 (umhelper_sem){++++}-{3:3}, at: usermodehelper_read_lock_wait+0x138/0x244 kernel/umh.c:250
2 locks held by kworker/u4:7/4946:
5 locks held by kworker/1:15/8758:
#0: ffff0000c45d7d38 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x664/0x1404 kernel/workqueue.c:2265
#1: ffff80001e837c20 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x6a8/0x1404 kernel/workqueue.c:2267
#2: ffff0000d0cbe190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:837 [inline]
#2: ffff0000d0cbe190 (&dev->mutex){....}-{3:3}, at: hub_event+0x1b0/0x42e4 drivers/usb/core/hub.c:5789
#3: ffff00013f52c190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:837 [inline]
#3: ffff00013f52c190 (&dev->mutex){....}-{3:3}, at: usb_disconnect+0xec/0x7b0 drivers/usb/core/hub.c:2260
#4: ffff0000f8e16118 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:837 [inline]
#4: ffff0000f8e16118 (&dev->mutex){....}-{3:3}, at: __device_driver_lock drivers/base/dd.c:1080 [inline]
#4: ffff0000f8e16118 (&dev->mutex){....}-{3:3}, at: device_release_driver_internal+0xbc/0x724 drivers/base/dd.c:1283
2 locks held by syz-executor.1/8994:
1 lock held by syz-executor.1/9006:
#0: ffff0000e253c188 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:768 [inline]
#0: ffff0000e253c188 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: lookup_slow+0x50/0x84 fs/namei.c:1706
2 locks held by syz-executor.1/9009:
#0: ffff0000f8b4a460 (sb_writers#33){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:393
#1: ffff0000e253c188 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
#1: ffff0000e253c188 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: open_last_lookups fs/namei.c:3549 [inline]
#1: ffff0000e253c188 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: path_openat+0x5ec/0x2548 fs/namei.c:3782
1 lock held by syz-executor.1/9019:
#0: ffff0000e253c188 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:768 [inline]
#0: ffff0000e253c188 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: open_last_lookups fs/namei.c:3551 [inline]
#0: ffff0000e253c188 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: path_openat+0x5dc/0x2548 fs/namei.c:3782
2 locks held by syz-executor.4/9114:
1 lock held by syz-executor.4/9115:
#0: ffff0000e253c6d0 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:768 [inline]
#0: ffff0000e253c6d0 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: lookup_slow+0x50/0x84 fs/namei.c:1706
2 locks held by syz-executor.4/9117:
#0: ffff0000f75d8460 (sb_writers#33){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:393
#1: ffff0000e253c6d0 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
#1: ffff0000e253c6d0 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: open_last_lookups fs/namei.c:3549 [inline]
#1: ffff0000e253c6d0 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: path_openat+0x5ec/0x2548 fs/namei.c:3782
1 lock held by syz-executor.4/9120:
#0: ffff0000e253c6d0 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:768 [inline]
#0: ffff0000e253c6d0 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: open_last_lookups fs/namei.c:3551 [inline]
#0: ffff0000e253c6d0 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: path_openat+0x5dc/0x2548 fs/namei.c:3782
2 locks held by syz-executor.0/9186:
1 lock held by syz-executor.0/9192:
#0: ffff0001010f4188 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:768 [inline]
#0: ffff0001010f4188 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: lookup_slow+0x50/0x84 fs/namei.c:1706
2 locks held by syz-executor.0/9195:
#0: ffff0000d9938460 (sb_writers#33){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:393
#1: ffff0001010f4188 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
#1: ffff0001010f4188 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: open_last_lookups fs/namei.c:3549 [inline]
#1: ffff0001010f4188 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: path_openat+0x5ec/0x2548 fs/namei.c:3782
1 lock held by syz-executor.0/9197:
#0: ffff0001010f4188 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:768 [inline]
#0: ffff0001010f4188 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: open_last_lookups fs/namei.c:3551 [inline]
#0: ffff0001010f4188 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: path_openat+0x5dc/0x2548 fs/namei.c:3782
1 lock held by syz-executor.4/9275:
#0: ffff800015a1a278 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:291 [inline]
#0: ffff800015a1a278 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x3e0/0x77c kernel/rcu/tree_exp.h:962
1 lock held by syz-executor.1/10345:
#0: ffff0000d0cbe190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:837 [inline]
#0: ffff0000d0cbe190 (&dev->mutex){....}-{3:3}, at: usbdev_open+0x13c/0x6c0 drivers/usb/core/devio.c:1052
1 lock held by syz-executor.0/10825:
=============================================
---
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: cd5d98c0556c Linux 6.1.86
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10c64c93180000
kernel config: https://syzkaller.appspot.com/x/.config?x=cc6a54650e83f88f
dashboard link: https://syzkaller.appspot.com/bug?extid=0e98e04ea2a9550a2596
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/35b2c3edb8aa/disk-cd5d98c0.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2a5efc7ec06c/vmlinux-cd5d98c0.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9f02d0ba73da/Image-cd5d98c0.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+0e98e0...@syzkaller.appspotmail.com
INFO: task syz-executor.1:9006 blocked for more than 143 seconds.
Not tainted 6.1.86-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.1 state:D stack:0 pid:9006 ppid:7986 flags:0x00000045
Call trace:
__switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0xee4/0x1c98 kernel/sched/core.c:6558
schedule+0xc4/0x170 kernel/sched/core.c:6634
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6693
rwsem_down_read_slowpath+0x534/0x858 kernel/locking/rwsem.c:1094
__down_read_common kernel/locking/rwsem.c:1261 [inline]
__down_read kernel/locking/rwsem.c:1274 [inline]
down_read+0xac/0x308 kernel/locking/rwsem.c:1522
inode_lock_shared include/linux/fs.h:768 [inline]
lookup_slow+0x50/0x84 fs/namei.c:1706
walk_component+0x280/0x36c fs/namei.c:1998
lookup_last fs/namei.c:2455 [inline]
path_lookupat+0x13c/0x3d0 fs/namei.c:2479
filename_lookup+0x1d4/0x4e0 fs/namei.c:2508
user_path_at_empty+0x5c/0x84 fs/namei.c:2907
user_path_at include/linux/namei.h:57 [inline]
do_mount fs/namespace.c:3391 [inline]
__do_sys_mount fs/namespace.c:3602 [inline]
__se_sys_mount fs/namespace.c:3579 [inline]
__arm64_sys_mount+0x428/0x594 fs/namespace.c:3579
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
INFO: task syz-executor.1:9009 blocked for more than 143 seconds.
Not tainted 6.1.86-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.1 state:D stack:0 pid:9009 ppid:7986 flags:0x0000000d
Call trace:
__switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0xee4/0x1c98 kernel/sched/core.c:6558
schedule+0xc4/0x170 kernel/sched/core.c:6634
rwsem_down_write_slowpath+0xc80/0x156c kernel/locking/rwsem.c:1189
__down_write_common kernel/locking/rwsem.c:1314 [inline]
__down_write kernel/locking/rwsem.c:1323 [inline]
down_write+0x84/0x88 kernel/locking/rwsem.c:1574
inode_lock include/linux/fs.h:758 [inline]
open_last_lookups fs/namei.c:3549 [inline]
path_openat+0x5ec/0x2548 fs/namei.c:3782
do_filp_open+0x1bc/0x3cc fs/namei.c:3812
do_sys_openat2+0x128/0x3d8 fs/open.c:1318
do_sys_open fs/open.c:1334 [inline]
__do_sys_openat fs/open.c:1350 [inline]
__se_sys_openat fs/open.c:1345 [inline]
__arm64_sys_openat+0x1f0/0x240 fs/open.c:1345
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
INFO: task syz-executor.1:9019 blocked for more than 143 seconds.
Not tainted 6.1.86-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.1 state:D stack:0 pid:9019 ppid:7986 flags:0x00000005
Call trace:
__switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0xee4/0x1c98 kernel/sched/core.c:6558
schedule+0xc4/0x170 kernel/sched/core.c:6634
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6693
rwsem_down_read_slowpath+0x534/0x858 kernel/locking/rwsem.c:1094
__down_read_common kernel/locking/rwsem.c:1261 [inline]
__down_read kernel/locking/rwsem.c:1274 [inline]
down_read+0xac/0x308 kernel/locking/rwsem.c:1522
inode_lock_shared include/linux/fs.h:768 [inline]
open_last_lookups fs/namei.c:3551 [inline]
path_openat+0x5dc/0x2548 fs/namei.c:3782
do_filp_open+0x1bc/0x3cc fs/namei.c:3812
do_sys_openat2+0x128/0x3d8 fs/open.c:1318
do_sys_open fs/open.c:1334 [inline]
__do_sys_openat fs/open.c:1350 [inline]
__se_sys_openat fs/open.c:1345 [inline]
__arm64_sys_openat+0x1f0/0x240 fs/open.c:1345
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffff800015a14e70 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:516
1 lock held by rcu_tasks_trace/13:
#0: ffff800015a15670 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:516
1 lock held by khungtaskd/28:
#0: ffff800015a14ca0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:349
2 locks held by kworker/u4:5/1755:
#0: ffff0001b436d198 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested kernel/sched/core.c:537 [inline]
#0: ffff0001b436d198 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock kernel/sched/sched.h:1354 [inline]
#0: ffff0001b436d198 (&rq->__lock){-.-.}-{2:2}, at: rq_lock kernel/sched/sched.h:1644 [inline]
#0: ffff0001b436d198 (&rq->__lock){-.-.}-{2:2}, at: __schedule+0x2c4/0x1c98 kernel/sched/core.c:6475
#1: ffff0001b4359b88 (&per_cpu_ptr(group->pcpu, cpu)->seq){-.-.}-{0:0}, at: psi_task_switch+0x3c0/0x618 kernel/sched/psi.c:1000
2 locks held by getty/3985:
#0: ffff0000d8380098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
#1: ffff80001bce02f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1214 drivers/tty/n_tty.c:2188
3 locks held by kworker/1:6/4291:
#0: ffff0000c0020938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x664/0x1404 kernel/workqueue.c:2265
#1: ffff80001e557c20 ((work_completion)(&fw_work->work)){+.+.}-{0:0}, at: process_one_work+0x6a8/0x1404 kernel/workqueue.c:2267
#2: ffff8000158c4510 (umhelper_sem){++++}-{3:3}, at: usermodehelper_read_lock_wait+0x138/0x244 kernel/umh.c:250
2 locks held by kworker/u4:7/4946:
5 locks held by kworker/1:15/8758:
#0: ffff0000c45d7d38 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x664/0x1404 kernel/workqueue.c:2265
#1: ffff80001e837c20 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x6a8/0x1404 kernel/workqueue.c:2267
#2: ffff0000d0cbe190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:837 [inline]
#2: ffff0000d0cbe190 (&dev->mutex){....}-{3:3}, at: hub_event+0x1b0/0x42e4 drivers/usb/core/hub.c:5789
#3: ffff00013f52c190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:837 [inline]
#3: ffff00013f52c190 (&dev->mutex){....}-{3:3}, at: usb_disconnect+0xec/0x7b0 drivers/usb/core/hub.c:2260
#4: ffff0000f8e16118 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:837 [inline]
#4: ffff0000f8e16118 (&dev->mutex){....}-{3:3}, at: __device_driver_lock drivers/base/dd.c:1080 [inline]
#4: ffff0000f8e16118 (&dev->mutex){....}-{3:3}, at: device_release_driver_internal+0xbc/0x724 drivers/base/dd.c:1283
2 locks held by syz-executor.1/8994:
1 lock held by syz-executor.1/9006:
#0: ffff0000e253c188 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:768 [inline]
#0: ffff0000e253c188 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: lookup_slow+0x50/0x84 fs/namei.c:1706
2 locks held by syz-executor.1/9009:
#0: ffff0000f8b4a460 (sb_writers#33){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:393
#1: ffff0000e253c188 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
#1: ffff0000e253c188 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: open_last_lookups fs/namei.c:3549 [inline]
#1: ffff0000e253c188 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: path_openat+0x5ec/0x2548 fs/namei.c:3782
1 lock held by syz-executor.1/9019:
#0: ffff0000e253c188 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:768 [inline]
#0: ffff0000e253c188 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: open_last_lookups fs/namei.c:3551 [inline]
#0: ffff0000e253c188 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: path_openat+0x5dc/0x2548 fs/namei.c:3782
2 locks held by syz-executor.4/9114:
1 lock held by syz-executor.4/9115:
#0: ffff0000e253c6d0 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:768 [inline]
#0: ffff0000e253c6d0 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: lookup_slow+0x50/0x84 fs/namei.c:1706
2 locks held by syz-executor.4/9117:
#0: ffff0000f75d8460 (sb_writers#33){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:393
#1: ffff0000e253c6d0 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
#1: ffff0000e253c6d0 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: open_last_lookups fs/namei.c:3549 [inline]
#1: ffff0000e253c6d0 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: path_openat+0x5ec/0x2548 fs/namei.c:3782
1 lock held by syz-executor.4/9120:
#0: ffff0000e253c6d0 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:768 [inline]
#0: ffff0000e253c6d0 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: open_last_lookups fs/namei.c:3551 [inline]
#0: ffff0000e253c6d0 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: path_openat+0x5dc/0x2548 fs/namei.c:3782
2 locks held by syz-executor.0/9186:
1 lock held by syz-executor.0/9192:
#0: ffff0001010f4188 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:768 [inline]
#0: ffff0001010f4188 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: lookup_slow+0x50/0x84 fs/namei.c:1706
2 locks held by syz-executor.0/9195:
#0: ffff0000d9938460 (sb_writers#33){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:393
#1: ffff0001010f4188 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
#1: ffff0001010f4188 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: open_last_lookups fs/namei.c:3549 [inline]
#1: ffff0001010f4188 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: path_openat+0x5ec/0x2548 fs/namei.c:3782
1 lock held by syz-executor.0/9197:
#0: ffff0001010f4188 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:768 [inline]
#0: ffff0001010f4188 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: open_last_lookups fs/namei.c:3551 [inline]
#0: ffff0001010f4188 (&type->i_mutex_dir_key#24){++++}-{3:3}, at: path_openat+0x5dc/0x2548 fs/namei.c:3782
1 lock held by syz-executor.4/9275:
#0: ffff800015a1a278 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:291 [inline]
#0: ffff800015a1a278 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x3e0/0x77c kernel/rcu/tree_exp.h:962
1 lock held by syz-executor.1/10345:
#0: ffff0000d0cbe190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:837 [inline]
#0: ffff0000d0cbe190 (&dev->mutex){....}-{3:3}, at: usbdev_open+0x13c/0x6c0 drivers/usb/core/devio.c:1052
1 lock held by syz-executor.0/10825:
=============================================
---
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