====================================================== WARNING: possible circular locking dependency detected 6.16.0-rc6-syzkaller-00002-g155a3c003e55 #0 Not tainted ------------------------------------------------------ syz.0.2034/12855 is trying to acquire lock: ffff888025244940 (&sbi->pipe_mutex){+.+.}-{4:4}, at: autofs_write fs/autofs/waitq.c:55 [inline] ffff888025244940 (&sbi->pipe_mutex){+.+.}-{4:4}, at: autofs_notify_daemon+0x4a6/0xd60 fs/autofs/waitq.c:164 but task is already holding lock: ffff88803778b488 (&of->mutex){+.+.}-{4:4}, at: kernfs_fop_write_iter+0x28f/0x510 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}: __mutex_lock_common kernel/locking/mutex.c:602 [inline] __mutex_lock+0x199/0xb90 kernel/locking/mutex.c:747 kernfs_seq_start+0x4d/0x240 fs/kernfs/file.c:154 seq_read_iter+0x2c1/0x12c0 fs/seq_file.c:225 kernfs_fop_read_iter+0x40f/0x5a0 fs/kernfs/file.c:279 new_sync_read fs/read_write.c:491 [inline] vfs_read+0x8bf/0xc60 fs/read_write.c:572 ksys_read+0x12a/0x250 fs/read_write.c:715 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcd/0x4c0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #2 (&p->lock){+.+.}-{4:4}: __mutex_lock_common kernel/locking/mutex.c:602 [inline] __mutex_lock+0x199/0xb90 kernel/locking/mutex.c:747 seq_read_iter+0xe1/0x12c0 fs/seq_file.c:182 kernfs_fop_read_iter+0x40f/0x5a0 fs/kernfs/file.c:279 copy_splice_read+0x615/0xba0 fs/splice.c:363 do_splice_read fs/splice.c:979 [inline] do_splice_read+0x285/0x370 fs/splice.c:953 splice_file_to_pipe+0x109/0x120 fs/splice.c:1289 do_sendfile+0x400/0xe50 fs/read_write.c:1376 __do_sys_sendfile64 fs/read_write.c:1431 [inline] __se_sys_sendfile64 fs/read_write.c:1417 [inline] __x64_sys_sendfile64+0x1d8/0x220 fs/read_write.c:1417 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcd/0x4c0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #1 (&pipe->mutex){+.+.}-{4:4}: __mutex_lock_common kernel/locking/mutex.c:602 [inline] __mutex_lock+0x199/0xb90 kernel/locking/mutex.c:747 anon_pipe_write+0x15d/0x1a70 fs/pipe.c:458 __kernel_write_iter+0x720/0xa90 fs/read_write.c:619 __kernel_write+0xf5/0x140 fs/read_write.c:639 autofs_write fs/autofs/waitq.c:57 [inline] autofs_notify_daemon+0x4db/0xd60 fs/autofs/waitq.c:164 autofs_wait+0x10ca/0x1a70 fs/autofs/waitq.c:426 autofs_do_expire_multi+0x14e/0x500 fs/autofs/expire.c:593 autofs_expire_multi+0x68/0x90 fs/autofs/expire.c:619 autofs_root_ioctl_unlocked+0x520/0x8d0 fs/autofs/root.c:897 autofs_root_ioctl+0x41/0x60 fs/autofs/root.c:910 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:907 [inline] __se_sys_ioctl fs/ioctl.c:893 [inline] __x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:893 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcd/0x4c0 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 kernel/locking/lockdep.c:3911 [inline] __lock_acquire+0x126f/0x1c90 kernel/locking/lockdep.c:5240 lock_acquire kernel/locking/lockdep.c:5871 [inline] lock_acquire+0x179/0x350 kernel/locking/lockdep.c:5828 __mutex_lock_common kernel/locking/mutex.c:602 [inline] __mutex_lock+0x199/0xb90 kernel/locking/mutex.c:747 autofs_write fs/autofs/waitq.c:55 [inline] autofs_notify_daemon+0x4a6/0xd60 fs/autofs/waitq.c:164 autofs_wait+0x10ca/0x1a70 fs/autofs/waitq.c:426 autofs_mount_wait+0x132/0x380 fs/autofs/root.c:255 autofs_d_automount+0x390/0x7f0 fs/autofs/root.c:401 follow_automount fs/namei.c:1455 [inline] __traverse_mounts+0x192/0x790 fs/namei.c:1500 traverse_mounts fs/namei.c:1529 [inline] handle_mounts fs/namei.c:1632 [inline] step_into+0x5aa/0x2270 fs/namei.c:1976 walk_component+0xfc/0x5b0 fs/namei.c:2144 lookup_last fs/namei.c:2639 [inline] path_lookupat+0x142/0x6d0 fs/namei.c:2663 filename_lookup+0x224/0x5f0 fs/namei.c:2692 kern_path+0x35/0x50 fs/namei.c:2825 lookup_bdev+0xd8/0x280 block/bdev.c:1205 resume_store+0x1d6/0x460 kernel/power/hibernate.c:1269 kobj_attr_store+0x55/0x80 lib/kobject.c:840 sysfs_kf_write+0xf2/0x150 fs/sysfs/file.c:145 kernfs_fop_write_iter+0x351/0x510 fs/kernfs/file.c:334 new_sync_write fs/read_write.c:593 [inline] vfs_write+0x6c7/0x1150 fs/read_write.c:686 ksys_write+0x12a/0x250 fs/read_write.c:738 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcd/0x4c0 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.0.2034/12855: #0: ffff888033add5f8 (&f->f_pos_lock){+.+.}-{4:4}, at: fdget_pos+0x2a2/0x370 fs/file.c:1217 #1: ffff888037dd2428 (sb_writers#8){.+.+}-{0:0}, at: ksys_write+0x12a/0x250 fs/read_write.c:738 #2: ffff88803778b488 (&of->mutex){+.+.}-{4:4}, at: kernfs_fop_write_iter+0x28f/0x510 fs/kernfs/file.c:325 #3: ffff888140a8a878 (kn->active#60){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x2b2/0x510 fs/kernfs/file.c:326 stack backtrace: CPU: 0 UID: 0 PID: 12855 Comm: syz.0.2034 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 lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120 print_circular_bug+0x275/0x350 kernel/locking/lockdep.c:2046 check_noncircular+0x14c/0x170 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 kernel/locking/lockdep.c:3911 [inline] __lock_acquire+0x126f/0x1c90 kernel/locking/lockdep.c:5240 lock_acquire kernel/locking/lockdep.c:5871 [inline] lock_acquire+0x179/0x350 kernel/locking/lockdep.c:5828 __mutex_lock_common kernel/locking/mutex.c:602 [inline] __mutex_lock+0x199/0xb90 kernel/locking/mutex.c:747 autofs_write fs/autofs/waitq.c:55 [inline] autofs_notify_daemon+0x4a6/0xd60 fs/autofs/waitq.c:164 autofs_wait+0x10ca/0x1a70 fs/autofs/waitq.c:426 autofs_mount_wait+0x132/0x380 fs/autofs/root.c:255 autofs_d_automount+0x390/0x7f0 fs/autofs/root.c:401 follow_automount fs/namei.c:1455 [inline] __traverse_mounts+0x192/0x790 fs/namei.c:1500 traverse_mounts fs/namei.c:1529 [inline] handle_mounts fs/namei.c:1632 [inline] step_into+0x5aa/0x2270 fs/namei.c:1976 walk_component+0xfc/0x5b0 fs/namei.c:2144 lookup_last fs/namei.c:2639 [inline] path_lookupat+0x142/0x6d0 fs/namei.c:2663 filename_lookup+0x224/0x5f0 fs/namei.c:2692 kern_path+0x35/0x50 fs/namei.c:2825 lookup_bdev+0xd8/0x280 block/bdev.c:1205 resume_store+0x1d6/0x460 kernel/power/hibernate.c:1269 kobj_attr_store+0x55/0x80 lib/kobject.c:840 sysfs_kf_write+0xf2/0x150 fs/sysfs/file.c:145 kernfs_fop_write_iter+0x351/0x510 fs/kernfs/file.c:334 new_sync_write fs/read_write.c:593 [inline] vfs_write+0x6c7/0x1150 fs/read_write.c:686 ksys_write+0x12a/0x250 fs/read_write.c:738 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcd/0x4c0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7ffb7478e929 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:00007ffb75650038 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 00007ffb749b6240 RCX: 00007ffb7478e929 RDX: 0000000000000012 RSI: 0000200000000040 RDI: 0000000000000009 RBP: 00007ffb74810b39 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007ffb749b6240 R15: 00007fff19001348 block device autoloading is deprecated and will be removed. PM: Image not found (code -22)