======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.0.17/5929 is trying to acquire lock:
ffff88802caf7668 (&p->lock){+.+.}-{3:3}, at: seq_read_iter+0xb1/0xd50 fs/seq_file.c:182

but task is already holding lock:
ffff88802274f068 (&pipe->mutex/1){+.+.}-{3:3}, at: splice_file_to_pipe+0x2a/0x110 fs/splice.c:1230

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #3 (&pipe->mutex/1){+.+.}-{3:3}:
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x129/0xcc0 kernel/locking/mutex.c:747
       __pipe_lock fs/pipe.c:103 [inline]
       pipe_write+0x1c7/0x1af0 fs/pipe.c:444
       __kernel_write_iter+0x274/0x670 fs/read_write.c:517
       __kernel_write+0xf0/0x140 fs/read_write.c:537
       autofs_write fs/autofs/waitq.c:57 [inline]
       autofs_notify_daemon+0x6ff/0xdc0 fs/autofs/waitq.c:164
       autofs_wait+0x1021/0x1a40 fs/autofs/waitq.c:426
       autofs_mount_wait+0x16b/0x320 fs/autofs/root.c:255
       autofs_d_automount+0x392/0x710 fs/autofs/root.c:401
       follow_automount fs/namei.c:1374 [inline]
       __traverse_mounts+0x323/0x5e0 fs/namei.c:1423
       traverse_mounts fs/namei.c:1452 [inline]
       handle_mounts fs/namei.c:1555 [inline]
       step_into+0x526/0xf10 fs/namei.c:1848
       lookup_last fs/namei.c:2467 [inline]
       path_lookupat+0x169/0x440 fs/namei.c:2491
       filename_lookup+0x1f4/0x510 fs/namei.c:2520
       kern_path+0x35/0x50 fs/namei.c:2618
       lookup_bdev+0xc1/0x280 block/bdev.c:993
       resume_store+0x16a/0x450 kernel/power/hibernate.c:1187
       kernfs_fop_write_iter+0x3b6/0x520 fs/kernfs/file.c:352
       call_write_iter include/linux/fs.h:2018 [inline]
       new_sync_write fs/read_write.c:491 [inline]
       vfs_write+0x43b/0x940 fs/read_write.c:584
       ksys_write+0x147/0x250 fs/read_write.c:637
       do_syscall_x64 arch/x86/entry/common.c:51 [inline]
       do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #2 (&sbi->pipe_mutex){+.+.}-{3:3}:
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x129/0xcc0 kernel/locking/mutex.c:747
       autofs_write fs/autofs/waitq.c:55 [inline]
       autofs_notify_daemon+0x6ec/0xdc0 fs/autofs/waitq.c:164
       autofs_wait+0x1021/0x1a40 fs/autofs/waitq.c:426
       autofs_mount_wait+0x16b/0x320 fs/autofs/root.c:255
       autofs_d_automount+0x392/0x710 fs/autofs/root.c:401
       follow_automount fs/namei.c:1374 [inline]
       __traverse_mounts+0x323/0x5e0 fs/namei.c:1423
       traverse_mounts fs/namei.c:1452 [inline]
       handle_mounts fs/namei.c:1555 [inline]
       step_into+0x526/0xf10 fs/namei.c:1848
       lookup_last fs/namei.c:2467 [inline]
       path_lookupat+0x169/0x440 fs/namei.c:2491
       filename_lookup+0x1f4/0x510 fs/namei.c:2520
       kern_path+0x35/0x50 fs/namei.c:2618
       lookup_bdev+0xc1/0x280 block/bdev.c:993
       resume_store+0x16a/0x450 kernel/power/hibernate.c:1187
       kernfs_fop_write_iter+0x3b6/0x520 fs/kernfs/file.c:352
       call_write_iter include/linux/fs.h:2018 [inline]
       new_sync_write fs/read_write.c:491 [inline]
       vfs_write+0x43b/0x940 fs/read_write.c:584
       ksys_write+0x147/0x250 fs/read_write.c:637
       do_syscall_x64 arch/x86/entry/common.c:51 [inline]
       do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #1 (&of->mutex){+.+.}-{3:3}:
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x129/0xcc0 kernel/locking/mutex.c:747
       kernfs_seq_start+0x5c/0x410 fs/kernfs/file.c:172
       seq_read_iter+0x3c8/0xd50 fs/seq_file.c:225
       call_read_iter include/linux/fs.h:2012 [inline]
       new_sync_read fs/read_write.c:389 [inline]
       vfs_read+0x431/0x920 fs/read_write.c:470
       ksys_read+0x147/0x250 fs/read_write.c:613
       do_syscall_x64 arch/x86/entry/common.c:51 [inline]
       do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #0 (&p->lock){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3134 [inline]
       check_prevs_add kernel/locking/lockdep.c:3253 [inline]
       validate_chain kernel/locking/lockdep.c:3869 [inline]
       __lock_acquire+0x2ddb/0x7c80 kernel/locking/lockdep.c:5137
       lock_acquire+0x197/0x410 kernel/locking/lockdep.c:5754
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x129/0xcc0 kernel/locking/mutex.c:747
       seq_read_iter+0xb1/0xd50 fs/seq_file.c:182
       call_read_iter include/linux/fs.h:2012 [inline]
       copy_splice_read+0x3c8/0x860 fs/splice.c:364
       splice_file_to_pipe+0x6e/0x110 fs/splice.c:1233
       do_sendfile+0x572/0xf70 fs/read_write.c:1261
       __do_sys_sendfile64 fs/read_write.c:1322 [inline]
       __se_sys_sendfile64+0x13f/0x190 fs/read_write.c:1308
       do_syscall_x64 arch/x86/entry/common.c:51 [inline]
       do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

other info that might help us debug this:

Chain exists of:
  &p->lock --> &sbi->pipe_mutex --> &pipe->mutex/1

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&pipe->mutex/1);
                               lock(&sbi->pipe_mutex);
                               lock(&pipe->mutex/1);
  lock(&p->lock);

 *** DEADLOCK ***

1 lock held by syz.0.17/5929:
 #0: ffff88802274f068 (&pipe->mutex/1){+.+.}-{3:3}, at: splice_file_to_pipe+0x2a/0x110 fs/splice.c:1230

stack backtrace:
CPU: 1 PID: 5929 Comm: syz.0.17 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x16c/0x230 lib/dump_stack.c:106
 check_noncircular+0x2bd/0x3c0 kernel/locking/lockdep.c:2187
 check_prev_add kernel/locking/lockdep.c:3134 [inline]
 check_prevs_add kernel/locking/lockdep.c:3253 [inline]
 validate_chain kernel/locking/lockdep.c:3869 [inline]
 __lock_acquire+0x2ddb/0x7c80 kernel/locking/lockdep.c:5137
 lock_acquire+0x197/0x410 kernel/locking/lockdep.c:5754
 __mutex_lock_common kernel/locking/mutex.c:603 [inline]
 __mutex_lock+0x129/0xcc0 kernel/locking/mutex.c:747
 seq_read_iter+0xb1/0xd50 fs/seq_file.c:182
 call_read_iter include/linux/fs.h:2012 [inline]
 copy_splice_read+0x3c8/0x860 fs/splice.c:364
 splice_file_to_pipe+0x6e/0x110 fs/splice.c:1233
 do_sendfile+0x572/0xf70 fs/read_write.c:1261
 __do_sys_sendfile64 fs/read_write.c:1322 [inline]
 __se_sys_sendfile64+0x13f/0x190 fs/read_write.c:1308
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fb66ff8f749
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:00007fb670ea1038 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 00007fb6701e6090 RCX: 00007fb66ff8f749
RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000000
RBP: 00007fb670013f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000004 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fb6701e6128 R14: 00007fb6701e6090 R15: 00007fff948f8918
 </TASK>