possible deadlock in iter_file_splice_write (4)

Status: closed as dup on 2024/06/05 11:05
Subsystems: overlayfs
[Documentation on labels]
Reported-by: syzbot+5ce16f43e888965f009d@syzkaller.appspotmail.com
First crash: 803d, last: 4d08h
Duplicate of
Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported
possible deadlock in kernfs_seq_start kernfs 4 syz, C done error 73 10d 837d
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [overlayfs?] possible deadlock in iter_file_splice_write (4) 1 (2) 2024/06/05 11:05
Similar bugs (7)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.6 possible deadlock in iter_file_splice_write 4 2 4d22h 5d17h 0/2 upstream: reported on 2026/08/07 15:15
upstream possible deadlock in iter_file_splice_write (3) overlayfs 4 24 840d 882d 0/29 closed as dup on 2024/03/14 09:27
linux-5.15 possible deadlock in iter_file_splice_write (3) 4 2 346d 350d 0/3 auto-obsoleted due to no activity on 2025/12/09 13:52
upstream possible deadlock in iter_file_splice_write overlayfs 4 1 2171d 2167d 0/29 auto-closed as invalid on 2020/12/30 21:45
upstream possible deadlock in iter_file_splice_write (2) overlayfs 4 syz, C done 2 1845d 1841d 0/29 closed as dup on 2021/07/28 14:57
linux-5.15 possible deadlock in iter_file_splice_write (2) 4 1 484d 484d 0/3 auto-obsoleted due to no activity on 2025/07/24 12:07
linux-5.15 possible deadlock in iter_file_splice_write 4 1 657d 657d 0/3 auto-obsoleted due to no activity on 2025/02/01 14:50

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Tainted: G             L     
------------------------------------------------------
syz.5.2058/14687 is trying to acquire lock:
ffff888056162c60 (&pipe->mutex){+.+.}-{4:4}, at: iter_file_splice_write+0x20a/0x1240 fs/splice.c:682

but task is already holding lock:
ffff88802bbb6450 (sb_writers#5){.+.+}-{0:0}, at: do_splice+0xe87/0x1970 fs/splice.c:1348

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #4 (sb_writers#5){.+.+}-{0:0}:
       percpu_down_read_internal include/linux/percpu-rwsem.h:53 [inline]
       percpu_down_read_freezable include/linux/percpu-rwsem.h:83 [inline]
       __sb_start_write include/linux/fs/super.h:19 [inline]
       sb_start_write+0x4d/0x1c0 include/linux/fs/super.h:125
       mnt_want_write+0x41/0x90 fs/namespace.c:494
       ovl_create_object+0x108/0x3b0 fs/overlayfs/dir.c:706
       lookup_open fs/namei.c:4508 [inline]
       open_last_lookups fs/namei.c:4608 [inline]
       path_openat+0x133a/0x3830 fs/namei.c:4860
       do_file_open+0x23e/0x4a0 fs/namei.c:4892
       do_sys_openat2+0x115/0x200 fs/open.c:1368
       do_sys_open fs/open.c:1374 [inline]
       __do_sys_openat fs/open.c:1390 [inline]
       __se_sys_openat fs/open.c:1385 [inline]
       __x64_sys_openat+0x138/0x170 fs/open.c:1385
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #3 (&ovl_i_mutex_dir_key[depth]){++++}-{4:4}:
       down_read+0x4a/0x330 kernel/locking/rwsem.c:1574
       inode_lock_shared include/linux/fs.h:1039 [inline]
       lookup_slow+0x46/0x70 fs/namei.c:1935
       walk_component fs/namei.c:2282 [inline]
       lookup_last fs/namei.c:2789 [inline]
       path_lookupat+0x3f5/0x8c0 fs/namei.c:2813
       filename_lookup+0x265/0x5d0 fs/namei.c:2842
       kern_path+0x3d/0x150 fs/namei.c:3036
       lookup_bdev+0xc8/0x290 block/bdev.c:1208
       resume_store+0x16f/0x4f0 kernel/power/hibernate.c:1278
       kernfs_fop_write_iter+0x3a4/0x540 fs/kernfs/file.c:345
       new_sync_write fs/read_write.c:595 [inline]
       vfs_write+0x612/0xba0 fs/read_write.c:687
       ksys_write+0x150/0x270 fs/read_write.c:739
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #2 (&of->mutex){+.+.}-{4:4}:
       __mutex_lock_common kernel/locking/mutex.c:646 [inline]
       __mutex_lock+0x19d/0x1550 kernel/locking/mutex.c:821
       kernfs_seq_start+0x5d/0x420 fs/kernfs/file.c:165
       seq_read_iter+0x37e/0xca0 fs/seq_file.c:226
       copy_splice_read+0x5ff/0xaa0 fs/splice.c:362
       do_splice_read fs/splice.c:980 [inline]
       splice_direct_to_actor+0x48b/0xcb0 fs/splice.c:1084
       do_splice_direct_actor fs/splice.c:1202 [inline]
       do_splice_direct+0x195/0x290 fs/splice.c:1228
       do_sendfile+0x52e/0x7c0 fs/read_write.c:1371
       __do_sys_sendfile64 fs/read_write.c:1432 [inline]
       __se_sys_sendfile64+0x144/0x1a0 fs/read_write.c:1418
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #1 (&p->lock){+.+.}-{4:4}:
       __mutex_lock_common kernel/locking/mutex.c:646 [inline]
       __mutex_lock+0x19d/0x1550 kernel/locking/mutex.c:821
       seq_read_iter+0xa4/0xca0 fs/seq_file.c:183
       proc_reg_read_iter+0x1b7/0x280 fs/proc/inode.c:299
       copy_splice_read+0x5ff/0xaa0 fs/splice.c:362
       do_splice_read fs/splice.c:980 [inline]
       splice_file_to_pipe+0x444/0x6b0 fs/splice.c:1290
       do_splice+0x11c2/0x1970 fs/splice.c:1374
       __do_splice fs/splice.c:1431 [inline]
       __do_sys_splice fs/splice.c:1634 [inline]
       __se_sys_splice+0x353/0x490 fs/splice.c:1616
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&pipe->mutex){+.+.}-{4:4}:
       check_prev_add kernel/locking/lockdep.c:3165 [inline]
       check_prevs_add kernel/locking/lockdep.c:3284 [inline]
       validate_chain kernel/locking/lockdep.c:3908 [inline]
       __lock_acquire+0x1520/0x2cf0 kernel/locking/lockdep.c:5237
       lock_acquire+0x106/0x350 kernel/locking/lockdep.c:5868
       __mutex_lock_common kernel/locking/mutex.c:646 [inline]
       __mutex_lock+0x19d/0x1550 kernel/locking/mutex.c:821
       iter_file_splice_write+0x20a/0x1240 fs/splice.c:682
       do_splice_from fs/splice.c:936 [inline]
       do_splice+0xf14/0x1970 fs/splice.c:1349
       __do_splice fs/splice.c:1431 [inline]
       __do_sys_splice fs/splice.c:1634 [inline]
       __se_sys_splice+0x353/0x490 fs/splice.c:1616
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0x174/0x580 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:
  &pipe->mutex --> &ovl_i_mutex_dir_key[depth] --> sb_writers#5

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  rlock(sb_writers#5);
                               lock(&ovl_i_mutex_dir_key[depth]);
                               lock(sb_writers#5);
  lock(&pipe->mutex);

 *** DEADLOCK ***

1 lock held by syz.5.2058/14687:
 #0: ffff88802bbb6450 (sb_writers#5){.+.+}-{0:0}, at: do_splice+0xe87/0x1970 fs/splice.c:1348

stack backtrace:
CPU: 0 UID: 0 PID: 14687 Comm: syz.5.2058 Tainted: G             L      syzkaller #0 PREEMPT(full) 
Tainted: [L]=SOFTLOCKUP
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/16/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 print_circular_bug+0x2e1/0x300 kernel/locking/lockdep.c:2043
 check_noncircular+0x12e/0x150 kernel/locking/lockdep.c:2175
 check_prev_add kernel/locking/lockdep.c:3165 [inline]
 check_prevs_add kernel/locking/lockdep.c:3284 [inline]
 validate_chain kernel/locking/lockdep.c:3908 [inline]
 __lock_acquire+0x1520/0x2cf0 kernel/locking/lockdep.c:5237
 lock_acquire+0x106/0x350 kernel/locking/lockdep.c:5868
 __mutex_lock_common kernel/locking/mutex.c:646 [inline]
 __mutex_lock+0x19d/0x1550 kernel/locking/mutex.c:821
 iter_file_splice_write+0x20a/0x1240 fs/splice.c:682
 do_splice_from fs/splice.c:936 [inline]
 do_splice+0xf14/0x1970 fs/splice.c:1349
 __do_splice fs/splice.c:1431 [inline]
 __do_sys_splice fs/splice.c:1634 [inline]
 __se_sys_splice+0x353/0x490 fs/splice.c:1616
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f2c6cf9e0d9
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f2c6de4b028 EFLAGS: 00000246 ORIG_RAX: 0000000000000113
RAX: ffffffffffffffda RBX: 00007f2c6d226090 RCX: 00007f2c6cf9e0d9
RDX: 000000000000000d RSI: 0000000000000000 RDI: 000000000000000a
RBP: 00007f2c6d035024 R08: 00000000088000cc R09: 1000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f2c6d226128 R14: 00007f2c6d226090 R15: 00007ffef673c808
 </TASK>

Crashes (47):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/08/09 00:36 upstream a59f57e2aa12 5d63f80b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in iter_file_splice_write
2026/08/02 22:19 upstream bd1dde877520 e611ffe1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in iter_file_splice_write
2026/02/24 09:53 upstream 7dff99b35460 41d2fa6a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in iter_file_splice_write
2025/11/12 06:23 upstream 24172e0d7990 4e1406b4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in iter_file_splice_write
2025/10/28 04:47 upstream fd57572253bc fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in iter_file_splice_write
2025/10/28 04:47 upstream fd57572253bc fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in iter_file_splice_write
2025/07/30 04:42 upstream 038d61fd6422 f8f2b4da .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in iter_file_splice_write
2025/07/21 20:21 upstream 89be9a83ccf1 0b3788a0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in iter_file_splice_write
2025/07/19 14:18 upstream 4871b7cb27f4 7117feec .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in iter_file_splice_write
2025/07/19 05:07 upstream d786aba32000 7117feec .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in iter_file_splice_write
2025/07/16 09:34 upstream 155a3c003e55 124ec9cc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in iter_file_splice_write
2025/04/26 23:46 upstream 5bc1018675ec c6b4fb39 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in iter_file_splice_write
2025/04/24 16:15 upstream a79be02bba5c 9882047a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in iter_file_splice_write
2025/02/24 04:45 upstream d082ecbc71e9 d34966d1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in iter_file_splice_write
2024/12/13 20:21 upstream f932fb9b4074 7cbfbb3a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in iter_file_splice_write
2024/12/13 03:58 upstream 150b567e0d57 3547e30f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in iter_file_splice_write
2024/11/25 07:56 upstream 9f16d5e6f220 68da6d95 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in iter_file_splice_write
2024/11/23 08:26 upstream 06afb0f36106 68da6d95 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in iter_file_splice_write
2024/11/23 08:18 upstream 06afb0f36106 68da6d95 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in iter_file_splice_write
2024/11/14 19:33 upstream 0a9b9d17f3a7 77f3eeb7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in iter_file_splice_write
2024/11/10 18:44 upstream de2f378f2b77 6b856513 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in iter_file_splice_write
2024/11/04 05:20 upstream b9021de3ec2f f00eed24 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in iter_file_splice_write
2024/11/02 02:22 upstream 6c52d4da1c74 f00eed24 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in iter_file_splice_write
2024/09/12 20:31 upstream 77f587896757 60e1a995 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in iter_file_splice_write
2024/09/10 16:28 upstream bc83b4d1f086 86aa7bd7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in iter_file_splice_write
2024/09/10 16:16 upstream bc83b4d1f086 86aa7bd7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in iter_file_splice_write
2024/08/24 14:54 upstream d2bafcf224f3 d7d32352 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in iter_file_splice_write
2024/06/18 07:55 upstream 2ccbdf43d5e7 ce6011bc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in iter_file_splice_write
2024/06/17 02:29 upstream 2ccbdf43d5e7 f429ab00 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in iter_file_splice_write
2024/06/06 03:36 upstream 2df0193e62cf 121701b6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in iter_file_splice_write
2024/06/06 01:20 upstream 71d7b52cc33b 5aa1a7c9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in iter_file_splice_write
2024/06/05 21:34 upstream 71d7b52cc33b 5aa1a7c9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in iter_file_splice_write
2024/06/05 00:36 upstream 32f88d65f01b e1e2c66e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in iter_file_splice_write
2024/06/04 00:37 upstream f06ce441457d a1feae05 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in iter_file_splice_write
2024/06/03 16:09 upstream c3f38fa61af7 0aba2352 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in iter_file_splice_write
2024/06/02 15:18 upstream 83814698cf48 3113787f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in iter_file_splice_write
2024/05/31 22:40 upstream d8ec19857b09 3113787f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in iter_file_splice_write
2024/05/31 18:46 upstream 4a4be1ad3a6e 0c378259 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in iter_file_splice_write
2026/06/01 16:52 linux-next f7af91adc230 8d8eeb3a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in iter_file_splice_write
2026/06/01 10:23 linux-next f7af91adc230 8d8eeb3a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in iter_file_splice_write
2026/05/25 15:30 linux-next c1ecb239fa34 c69befb3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in iter_file_splice_write
2026/05/22 12:20 linux-next 550604d6c9b9 e16cf9f3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in iter_file_splice_write
2026/01/18 09:58 linux-next 46fe65a2c28e d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in iter_file_splice_write
2025/10/29 02:18 linux-next f7d2388eeec2 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in iter_file_splice_write
2025/08/07 06:45 linux-next b7d4e259682c 4bd24a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in iter_file_splice_write
2025/06/01 14:26 linux-next 3a83b350b5be 3d2f584d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in iter_file_splice_write
2025/02/23 07:01 linux-next e5d3fd687aac d34966d1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in iter_file_splice_write
* Struck through repros no longer work on HEAD.