====================================================== WARNING: possible circular locking dependency detected 6.16.0-rc6-syzkaller-00002-g155a3c003e55 #0 Not tainted ------------------------------------------------------ syz.7.3173/20751 is trying to acquire lock: ffff888067675140 (&sbi->pipe_mutex){+.+.}-{4:4}, at: autofs_write fs/autofs/waitq.c:55 [inline] ffff888067675140 (&sbi->pipe_mutex){+.+.}-{4:4}, at: autofs_notify_daemon+0x735/0xe50 fs/autofs/waitq.c:164 but task is already holding lock: ffff8880591efc88 (&of->mutex){+.+.}-{4:4}, at: kernfs_fop_write_iter+0x1e0/0x4f0 fs/kernfs/file.c:325 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #3 (&of->mutex){+.+.}-{4:4}: lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5871 __mutex_lock_common kernel/locking/mutex.c:602 [inline] __mutex_lock+0x182/0xe80 kernel/locking/mutex.c:747 kernfs_seq_start+0x55/0x3c0 fs/kernfs/file.c:154 seq_read_iter+0x3ef/0xe10 fs/seq_file.c:225 copy_splice_read+0x54f/0x9b0 fs/splice.c:363 do_splice_read fs/splice.c:979 [inline] splice_file_to_pipe+0x273/0x440 fs/splice.c:1289 do_sendfile+0x475/0x7e0 fs/read_write.c:1376 __do_sys_sendfile64 fs/read_write.c:1431 [inline] __se_sys_sendfile64+0x13e/0x190 fs/read_write.c:1417 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #2 (&p->lock){+.+.}-{4:4}: lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5871 __mutex_lock_common kernel/locking/mutex.c:602 [inline] __mutex_lock+0x182/0xe80 kernel/locking/mutex.c:747 seq_read_iter+0xb7/0xe10 fs/seq_file.c:182 copy_splice_read+0x54f/0x9b0 fs/splice.c:363 do_splice_read fs/splice.c:979 [inline] splice_file_to_pipe+0x273/0x440 fs/splice.c:1289 do_sendfile+0x475/0x7e0 fs/read_write.c:1376 __do_sys_sendfile64 fs/read_write.c:1431 [inline] __se_sys_sendfile64+0x13e/0x190 fs/read_write.c:1417 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #1 (&pipe->mutex){+.+.}-{4:4}: lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5871 __mutex_lock_common kernel/locking/mutex.c:602 [inline] __mutex_lock+0x182/0xe80 kernel/locking/mutex.c:747 anon_pipe_write+0x16a/0x1360 fs/pipe.c:458 __kernel_write_iter+0x3ec/0x860 fs/read_write.c:619 __kernel_write+0xef/0x150 fs/read_write.c:639 autofs_write fs/autofs/waitq.c:57 [inline] autofs_notify_daemon+0x748/0xe50 fs/autofs/waitq.c:164 autofs_wait+0x11dc/0x1870 fs/autofs/waitq.c:426 autofs_mount_wait+0x16b/0x330 fs/autofs/root.c:255 autofs_d_automount+0x393/0x720 fs/autofs/root.c:401 follow_automount fs/namei.c:1455 [inline] __traverse_mounts+0x308/0x5b0 fs/namei.c:1500 traverse_mounts fs/namei.c:1529 [inline] handle_mounts fs/namei.c:1632 [inline] step_into+0x534/0xf30 fs/namei.c:1976 walk_component fs/namei.c:2144 [inline] link_path_walk+0x77b/0xea0 fs/namei.c:2506 path_lookupat+0x97/0x430 fs/namei.c:2662 filename_lookup+0x212/0x570 fs/namei.c:2692 user_path_at+0x3a/0x60 fs/namei.c:3136 bpf_obj_do_get kernel/bpf/inode.c:503 [inline] bpf_obj_get_user+0xa9/0x430 kernel/bpf/inode.c:538 __sys_bpf+0x71e/0x860 kernel/bpf/syscall.c:5842 __do_sys_bpf kernel/bpf/syscall.c:5943 [inline] __se_sys_bpf kernel/bpf/syscall.c:5941 [inline] __x64_sys_bpf+0x7c/0x90 kernel/bpf/syscall.c:5941 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #0 (&sbi->pipe_mutex){+.+.}-{4:4}: check_prev_add kernel/locking/lockdep.c:3168 [inline] check_prevs_add kernel/locking/lockdep.c:3287 [inline] validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3911 __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5240 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5871 __mutex_lock_common kernel/locking/mutex.c:602 [inline] __mutex_lock+0x182/0xe80 kernel/locking/mutex.c:747 autofs_write fs/autofs/waitq.c:55 [inline] autofs_notify_daemon+0x735/0xe50 fs/autofs/waitq.c:164 autofs_wait+0x11dc/0x1870 fs/autofs/waitq.c:426 autofs_mount_wait+0x16b/0x330 fs/autofs/root.c:255 autofs_d_automount+0x393/0x720 fs/autofs/root.c:401 follow_automount fs/namei.c:1455 [inline] __traverse_mounts+0x308/0x5b0 fs/namei.c:1500 traverse_mounts fs/namei.c:1529 [inline] handle_mounts fs/namei.c:1632 [inline] step_into+0x534/0xf30 fs/namei.c:1976 lookup_last fs/namei.c:2639 [inline] path_lookupat+0x163/0x430 fs/namei.c:2663 filename_lookup+0x212/0x570 fs/namei.c:2692 kern_path+0x35/0x50 fs/namei.c:2825 lookup_bdev+0xc0/0x280 block/bdev.c:1205 resume_store+0x169/0x460 kernel/power/hibernate.c:1269 kernfs_fop_write_iter+0x378/0x4f0 fs/kernfs/file.c:334 new_sync_write fs/read_write.c:593 [inline] vfs_write+0x54b/0xa90 fs/read_write.c:686 ksys_write+0x145/0x250 fs/read_write.c:738 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f other info that might help us debug this: Chain exists of: &sbi->pipe_mutex --> &p->lock --> &of->mutex Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&of->mutex); lock(&p->lock); lock(&of->mutex); lock(&sbi->pipe_mutex); *** DEADLOCK *** 4 locks held by syz.7.3173/20751: #0: ffff88805e3362b8 (&f->f_pos_lock){+.+.}-{4:4}, at: fdget_pos+0x247/0x320 fs/file.c:1217 #1: ffff88803466e428 (sb_writers#7){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:3096 [inline] #1: ffff88803466e428 (sb_writers#7){.+.+}-{0:0}, at: vfs_write+0x211/0xa90 fs/read_write.c:682 #2: ffff8880591efc88 (&of->mutex){+.+.}-{4:4}, at: kernfs_fop_write_iter+0x1e0/0x4f0 fs/kernfs/file.c:325 #3: ffff888140ea33c8 (kn->active#66){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x203/0x4f0 fs/kernfs/file.c:326 stack backtrace: CPU: 0 UID: 0 PID: 20751 Comm: syz.7.3173 Not tainted 6.16.0-rc6-syzkaller-00002-g155a3c003e55 #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 Call Trace: dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_circular_bug+0x2ee/0x310 kernel/locking/lockdep.c:2046 check_noncircular+0x134/0x160 kernel/locking/lockdep.c:2178 check_prev_add kernel/locking/lockdep.c:3168 [inline] check_prevs_add kernel/locking/lockdep.c:3287 [inline] validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3911 __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5240 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5871 __mutex_lock_common kernel/locking/mutex.c:602 [inline] __mutex_lock+0x182/0xe80 kernel/locking/mutex.c:747 autofs_write fs/autofs/waitq.c:55 [inline] autofs_notify_daemon+0x735/0xe50 fs/autofs/waitq.c:164 autofs_wait+0x11dc/0x1870 fs/autofs/waitq.c:426 autofs_mount_wait+0x16b/0x330 fs/autofs/root.c:255 autofs_d_automount+0x393/0x720 fs/autofs/root.c:401 follow_automount fs/namei.c:1455 [inline] __traverse_mounts+0x308/0x5b0 fs/namei.c:1500 traverse_mounts fs/namei.c:1529 [inline] handle_mounts fs/namei.c:1632 [inline] step_into+0x534/0xf30 fs/namei.c:1976 lookup_last fs/namei.c:2639 [inline] path_lookupat+0x163/0x430 fs/namei.c:2663 filename_lookup+0x212/0x570 fs/namei.c:2692 kern_path+0x35/0x50 fs/namei.c:2825 lookup_bdev+0xc0/0x280 block/bdev.c:1205 resume_store+0x169/0x460 kernel/power/hibernate.c:1269 kernfs_fop_write_iter+0x378/0x4f0 fs/kernfs/file.c:334 new_sync_write fs/read_write.c:593 [inline] vfs_write+0x54b/0xa90 fs/read_write.c:686 ksys_write+0x145/0x250 fs/read_write.c:738 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f6ece78e929 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f6ecc1b2038 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 00007f6ece9b6240 RCX: 00007f6ece78e929 RDX: 0000000000000012 RSI: 0000200000000040 RDI: 0000000000000009 RBP: 00007f6ece810b39 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007f6ece9b6240 R15: 00007ffd2ad59b88 block device autoloading is deprecated and will be removed. PM: Image not found (code -22)