====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Tainted: G L ------------------------------------------------------ kworker/u8:7/1024 is trying to acquire lock: ffff88802136e878 (&of->mutex){+.+.}-{4:4}, at: kernfs_seq_start+0x5d/0x420 fs/kernfs/file.c:165 but task is already holding lock: ffff888037d1fa68 (&p->lock){+.+.}-{4:4}, at: seq_read_iter+0xa5/0xcb0 fs/seq_file.c:183 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #3 (&p->lock){+.+.}-{4:4}: __mutex_lock_common kernel/locking/rtmutex_api.c:561 [inline] mutex_lock_nested+0x55/0x1d0 kernel/locking/rtmutex_api.c:580 seq_read_iter+0xa5/0xcb0 fs/seq_file.c:183 proc_reg_read_iter+0x1bf/0x290 fs/proc/inode.c:299 copy_splice_read+0x605/0xab0 fs/splice.c:362 do_splice_read fs/splice.c:980 [inline] splice_file_to_pipe+0x4b7/0x730 fs/splice.c:1318 do_splice+0x1267/0x1a80 fs/splice.c:1402 __do_splice fs/splice.c:1459 [inline] __do_sys_splice fs/splice.c:1662 [inline] __se_sys_splice+0x353/0x490 fs/splice.c:1644 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline] do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #2 (&pipe->mutex){+.+.}-{4:4}: __mutex_lock_common kernel/locking/rtmutex_api.c:561 [inline] mutex_lock_nested+0x55/0x1d0 kernel/locking/rtmutex_api.c:580 anon_pipe_prefill_and_lock fs/pipe.c:165 [inline] anon_pipe_write+0x292/0x1a90 fs/pipe.c:534 __kernel_write_iter+0x453/0x8f0 fs/read_write.c:621 __kernel_write+0x106/0x170 fs/read_write.c:641 autofs_write fs/autofs/waitq.c:70 [inline] autofs_notify_daemon+0x7aa/0xf60 fs/autofs/waitq.c:177 autofs_wait+0x11c8/0x18d0 fs/autofs/waitq.c:439 autofs_mount_wait+0x16b/0x390 fs/autofs/root.c:256 autofs_d_automount+0x64e/0x810 fs/autofs/root.c:410 follow_automount fs/namei.c:1571 [inline] __traverse_mounts+0x2fe/0x5d0 fs/namei.c:1624 traverse_mounts fs/namei.c:1653 [inline] handle_mounts fs/namei.c:1755 [inline] step_into_slowpath+0x4ba/0x820 fs/namei.c:2110 step_into fs/namei.c:2158 [inline] walk_component fs/namei.c:2294 [inline] lookup_last fs/namei.c:2795 [inline] path_lookupat+0x433/0x8c0 fs/namei.c:2819 filename_lookup+0x265/0x5d0 fs/namei.c:2848 user_path_at+0x40/0x160 fs/namei.c:3647 do_mount fs/namespace.c:4347 [inline] __do_sys_mount fs/namespace.c:4565 [inline] __se_sys_mount+0x2dc/0x420 fs/namespace.c:4542 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline] do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #1 (&sbi->pipe_mutex){+.+.}-{4:4}: __mutex_lock_common kernel/locking/rtmutex_api.c:561 [inline] mutex_lock_nested+0x55/0x1d0 kernel/locking/rtmutex_api.c:580 autofs_write fs/autofs/waitq.c:68 [inline] autofs_notify_daemon+0x797/0xf60 fs/autofs/waitq.c:177 autofs_wait+0x11c8/0x18d0 fs/autofs/waitq.c:439 autofs_mount_wait+0x16b/0x390 fs/autofs/root.c:256 autofs_d_automount+0x64e/0x810 fs/autofs/root.c:410 follow_automount fs/namei.c:1571 [inline] __traverse_mounts+0x2fe/0x5d0 fs/namei.c:1624 traverse_mounts fs/namei.c:1653 [inline] handle_mounts fs/namei.c:1755 [inline] step_into_slowpath+0x4ba/0x820 fs/namei.c:2110 step_into fs/namei.c:2158 [inline] walk_component fs/namei.c:2294 [inline] lookup_last fs/namei.c:2795 [inline] path_lookupat+0x433/0x8c0 fs/namei.c:2819 filename_lookup+0x265/0x5d0 fs/namei.c:2848 kern_path+0x3d/0x150 fs/namei.c:3042 lookup_bdev+0xc8/0x2b0 block/bdev.c:1268 resume_store+0x181/0x500 kernel/power/hibernate.c:1286 kernfs_fop_write_iter+0x3a5/0x540 fs/kernfs/file.c:345 new_sync_write fs/read_write.c:595 [inline] vfs_write+0x61e/0xbb0 fs/read_write.c:687 ksys_write+0x156/0x270 fs/read_write.c:739 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline] do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #0 (&of->mutex){+.+.}-{4:4}: check_prev_add kernel/locking/lockdep.c:3209 [inline] check_prevs_add kernel/locking/lockdep.c:3328 [inline] validate_chain kernel/locking/lockdep.c:3952 [inline] __lock_acquire+0x164c/0x2de0 kernel/locking/lockdep.c:5288 lock_acquire+0x115/0x350 kernel/locking/lockdep.c:5942 __mutex_lock_common kernel/locking/rtmutex_api.c:561 [inline] mutex_lock_nested+0x55/0x1d0 kernel/locking/rtmutex_api.c:580 kernfs_seq_start+0x5d/0x420 fs/kernfs/file.c:165 traverse+0x192/0x620 fs/seq_file.c:107 seq_read_iter+0xb6b/0xcb0 fs/seq_file.c:196 lo_rw_aio+0xe1b/0x1100 include/linux/percpu-rwsem.h:-1 do_req_filebacked drivers/block/loop.c:432 [inline] loop_handle_cmd drivers/block/loop.c:1847 [inline] loop_process_work+0x92f/0x11d0 drivers/block/loop.c:1882 process_one_work kernel/workqueue.c:3495 [inline] process_scheduled_works+0xc3d/0x1630 kernel/workqueue.c:3578 worker_thread+0xa47/0xfb0 kernel/workqueue.c:3659 kthread+0x38b/0x470 kernel/kthread.c:436 ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 other info that might help us debug this: Chain exists of: &of->mutex --> &pipe->mutex --> &p->lock Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&p->lock); lock(&pipe->mutex); lock(&p->lock); lock(&of->mutex); *** DEADLOCK *** locks held by kworker/u8:7/1024: 3, last CPU#1: #0: ffff888030b98940 ((wq_completion)loop9){+.+.}-{0:0}, at: rcu_lock_acquire include/linux/rcupdate.h:309 [inline] #0: ffff888030b98940 ((wq_completion)loop9){+.+.}-{0:0}, at: rcu_read_lock include/linux/rcupdate.h:849 [inline] #0: ffff888030b98940 ((wq_completion)loop9){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3460 [inline] #0: ffff888030b98940 ((wq_completion)loop9){+.+.}-{0:0}, at: process_scheduled_works+0x97a/0x1630 kernel/workqueue.c:3578 #1: ffffc90006117c40 ((work_completion)(&worker->work)){+.+.}-{0:0}, at: rcu_lock_acquire include/linux/rcupdate.h:309 [inline] #1: ffffc90006117c40 ((work_completion)(&worker->work)){+.+.}-{0:0}, at: rcu_read_lock include/linux/rcupdate.h:849 [inline] #1: ffffc90006117c40 ((work_completion)(&worker->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3460 [inline] #1: ffffc90006117c40 ((work_completion)(&worker->work)){+.+.}-{0:0}, at: process_scheduled_works+0x97a/0x1630 kernel/workqueue.c:3578 #2: ffff888037d1fa68 (&p->lock){+.+.}-{4:4}, at: seq_read_iter+0xa5/0xcb0 fs/seq_file.c:183 stack backtrace: CPU: 1 UID: 0 PID: 1024 Comm: kworker/u8:7 Tainted: G L syzkaller #0 PREEMPT_{RT,(full)} Tainted: [L]=SOFTLOCKUP Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/15/2026 Workqueue: loop9 loop_workfn Call Trace: dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120 print_circular_bug+0x2e2/0x300 kernel/locking/lockdep.c:2087 check_noncircular+0x12f/0x150 kernel/locking/lockdep.c:2219 check_prev_add kernel/locking/lockdep.c:3209 [inline] check_prevs_add kernel/locking/lockdep.c:3328 [inline] validate_chain kernel/locking/lockdep.c:3952 [inline] __lock_acquire+0x164c/0x2de0 kernel/locking/lockdep.c:5288 lock_acquire+0x115/0x350 kernel/locking/lockdep.c:5942 __mutex_lock_common kernel/locking/rtmutex_api.c:561 [inline] mutex_lock_nested+0x55/0x1d0 kernel/locking/rtmutex_api.c:580 kernfs_seq_start+0x5d/0x420 fs/kernfs/file.c:165 traverse+0x192/0x620 fs/seq_file.c:107 seq_read_iter+0xb6b/0xcb0 fs/seq_file.c:196 lo_rw_aio+0xe1b/0x1100 include/linux/percpu-rwsem.h:-1 do_req_filebacked drivers/block/loop.c:432 [inline] loop_handle_cmd drivers/block/loop.c:1847 [inline] loop_process_work+0x92f/0x11d0 drivers/block/loop.c:1882 process_one_work kernel/workqueue.c:3495 [inline] process_scheduled_works+0xc3d/0x1630 kernel/workqueue.c:3578 worker_thread+0xa47/0xfb0 kernel/workqueue.c:3659 kthread+0x38b/0x470 kernel/kthread.c:436 ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245