syzbot


possible deadlock in kernfs_fop_write_iter (2)

Status: upstream: reported on 2024/10/14 06:57
Subsystems: kernfs
[Documentation on labels]
Reported-by: syzbot+1cfd86253864f61b533e@syzkaller.appspotmail.com
First crash: 444d, last: 2h07m
Discussions (9)
Title Replies (including bot) Last reply
[syzbot] Monthly kernfs report (Dec 2025) 0 (1) 2025/12/26 07:48
[syzbot] Monthly kernfs report (Oct 2025) 0 (1) 2025/10/24 18:48
[syzbot] Monthly kernfs report (Jul 2025) 0 (1) 2025/07/23 10:04
[syzbot] Monthly kernfs report (May 2025) 0 (1) 2025/05/21 14:55
[syzbot] Monthly kernfs report (Apr 2025) 0 (1) 2025/04/22 10:11
[syzbot] Monthly kernfs report (Mar 2025) 0 (1) 2025/03/19 21:29
[syzbot] Monthly kernfs report (Feb 2025) 0 (1) 2025/02/16 21:54
[syzbot] Monthly kernfs report (Dec 2024) 0 (1) 2024/12/16 09:45
[syzbot] [kernfs?] possible deadlock in kernfs_fop_write_iter (2) 0 (1) 2024/10/14 06:57
Similar bugs (4)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in kernfs_fop_write_iter kernfs 4 14 519d 544d 0/29 auto-obsoleted due to no activity on 2024/10/05 00:05
linux-6.6 possible deadlock in kernfs_fop_write_iter 4 1 122d 122d 0/2 auto-obsoleted due to no activity on 2025/12/05 21:08
linux-5.15 possible deadlock in kernfs_fop_write_iter 4 3 324d 421d 0/3 auto-obsoleted due to no activity on 2025/05/17 20:05
linux-5.15 possible deadlock in kernfs_fop_write_iter (2) 4 1 210d 210d 0/3 auto-obsoleted due to no activity on 2025/09/09 09:34

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.8.2494/15030 is trying to acquire lock:
ffff888029aabc78 (&of->mutex){+.+.}-{4:4}, at: kernfs_fop_write_iter+0x1df/0x540 fs/kernfs/file.c:343

but task is already holding lock:
ffff88802a292858 (&pipe->mutex){+.+.}-{4:4}, at: iter_file_splice_write+0x1e6/0x10b0 fs/splice.c:683

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (&pipe->mutex){+.+.}-{4:4}:
       __mutex_lock_common kernel/locking/rtmutex_api.c:533 [inline]
       mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:552
       anon_pipe_write+0x160/0x1460 fs/pipe.c:458
       __kernel_write_iter+0x48a/0x920 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+0x721/0xe20 fs/autofs/waitq.c:164
       autofs_wait+0x11f7/0x1900 fs/autofs/waitq.c:426
       autofs_mount_wait+0x16b/0x390 fs/autofs/root.c:255
       autofs_d_automount+0x64f/0x820 fs/autofs/root.c:409
       follow_automount fs/namei.c:1499 [inline]
       __traverse_mounts+0x301/0x5e0 fs/namei.c:1552
       traverse_mounts fs/namei.c:1581 [inline]
       handle_mounts fs/namei.c:1686 [inline]
       step_into_slowpath+0x469/0x7d0 fs/namei.c:2043
       step_into fs/namei.c:2091 [inline]
       walk_component fs/namei.c:2227 [inline]
       lookup_last fs/namei.c:2722 [inline]
       path_lookupat+0x433/0x8c0 fs/namei.c:2746
       filename_lookup+0x212/0x570 fs/namei.c:2775
       kern_path+0x35/0x50 fs/namei.c:2987
       lookup_bdev+0xc0/0x280 block/bdev.c:1222
       resume_store+0x169/0x480 kernel/power/hibernate.c:1306
       kernfs_fop_write_iter+0x3b0/0x540 fs/kernfs/file.c:352
       new_sync_write fs/read_write.c:593 [inline]
       vfs_write+0x5d5/0xb40 fs/read_write.c:686
       ksys_write+0x14b/0x260 fs/read_write.c:738
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xec/0xf80 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #1 (&sbi->pipe_mutex){+.+.}-{4:4}:
       __mutex_lock_common kernel/locking/rtmutex_api.c:533 [inline]
       mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:552
       autofs_write fs/autofs/waitq.c:55 [inline]
       autofs_notify_daemon+0x70e/0xe20 fs/autofs/waitq.c:164
       autofs_wait+0x11f7/0x1900 fs/autofs/waitq.c:426
       autofs_mount_wait+0x16b/0x390 fs/autofs/root.c:255
       autofs_d_automount+0x64f/0x820 fs/autofs/root.c:409
       follow_automount fs/namei.c:1499 [inline]
       __traverse_mounts+0x301/0x5e0 fs/namei.c:1552
       traverse_mounts fs/namei.c:1581 [inline]
       handle_mounts fs/namei.c:1686 [inline]
       step_into_slowpath+0x469/0x7d0 fs/namei.c:2043
       step_into fs/namei.c:2091 [inline]
       walk_component fs/namei.c:2227 [inline]
       lookup_last fs/namei.c:2722 [inline]
       path_lookupat+0x433/0x8c0 fs/namei.c:2746
       filename_lookup+0x212/0x570 fs/namei.c:2775
       kern_path+0x35/0x50 fs/namei.c:2987
       lookup_bdev+0xc0/0x280 block/bdev.c:1222
       resume_store+0x169/0x480 kernel/power/hibernate.c:1306
       kernfs_fop_write_iter+0x3b0/0x540 fs/kernfs/file.c:352
       new_sync_write fs/read_write.c:593 [inline]
       vfs_write+0x5d5/0xb40 fs/read_write.c:686
       ksys_write+0x14b/0x260 fs/read_write.c:738
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xec/0xf80 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&of->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+0x15a6/0x2cf0 kernel/locking/lockdep.c:5237
       lock_acquire+0x107/0x340 kernel/locking/lockdep.c:5868
       __mutex_lock_common kernel/locking/rtmutex_api.c:533 [inline]
       mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:552
       kernfs_fop_write_iter+0x1df/0x540 fs/kernfs/file.c:343
       iter_file_splice_write+0x977/0x10b0 fs/splice.c:738
       do_splice_from fs/splice.c:938 [inline]
       do_splice+0xc8e/0x1680 fs/splice.c:1351
       __do_splice fs/splice.c:1433 [inline]
       __do_sys_splice fs/splice.c:1636 [inline]
       __se_sys_splice+0x2e1/0x460 fs/splice.c:1618
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xec/0xf80 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:
  &of->mutex --> &sbi->pipe_mutex --> &pipe->mutex

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&pipe->mutex);
                               lock(&sbi->pipe_mutex);
                               lock(&pipe->mutex);
  lock(&of->mutex);

 *** DEADLOCK ***

2 locks held by syz.8.2494/15030:
 #0: ffff888033888480 (sb_writers#10){.+.+}-{0:0}, at: do_splice+0xc11/0x1680 fs/splice.c:1350
 #1: ffff88802a292858 (&pipe->mutex){+.+.}-{4:4}, at: iter_file_splice_write+0x1e6/0x10b0 fs/splice.c:683

stack backtrace:
CPU: 0 UID: 0 PID: 15030 Comm: syz.8.2494 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 print_circular_bug+0x2e2/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+0x15a6/0x2cf0 kernel/locking/lockdep.c:5237
 lock_acquire+0x107/0x340 kernel/locking/lockdep.c:5868
 __mutex_lock_common kernel/locking/rtmutex_api.c:533 [inline]
 mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:552
 kernfs_fop_write_iter+0x1df/0x540 fs/kernfs/file.c:343
 iter_file_splice_write+0x977/0x10b0 fs/splice.c:738
 do_splice_from fs/splice.c:938 [inline]
 do_splice+0xc8e/0x1680 fs/splice.c:1351
 __do_splice fs/splice.c:1433 [inline]
 __do_sys_splice fs/splice.c:1636 [inline]
 __se_sys_splice+0x2e1/0x460 fs/splice.c:1618
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xec/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f095a0df749
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:00007f0958346038 EFLAGS: 00000246 ORIG_RAX: 0000000000000113
RAX: ffffffffffffffda RBX: 00007f095a335fa0 RCX: 00007f095a0df749
RDX: 0000000000000006 RSI: 0000000000000000 RDI: 0000000000000003
RBP: 00007f095a163f91 R08: 0000000000001000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f095a336038 R14: 00007f095a335fa0 R15: 00007ffcd8ecd908
 </TASK>

Crashes (112):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/12/28 08:35 upstream d26143bb38e2 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in kernfs_fop_write_iter
2025/12/28 07:23 upstream d26143bb38e2 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in kernfs_fop_write_iter
2025/12/26 18:16 upstream ccd1cdca5cd4 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in kernfs_fop_write_iter
2025/12/26 16:51 upstream ccd1cdca5cd4 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in kernfs_fop_write_iter
2025/12/26 15:20 upstream ccd1cdca5cd4 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in kernfs_fop_write_iter
2025/12/26 01:47 upstream ccd1cdca5cd4 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in kernfs_fop_write_iter
2025/12/24 20:14 upstream b927546677c8 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in kernfs_fop_write_iter
2025/12/24 06:04 upstream b927546677c8 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in kernfs_fop_write_iter
2025/12/24 02:08 upstream b927546677c8 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in kernfs_fop_write_iter
2025/12/23 22:50 upstream b927546677c8 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in kernfs_fop_write_iter
2025/12/23 04:35 upstream b927546677c8 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in kernfs_fop_write_iter
2025/12/22 17:42 upstream 9448598b22c5 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in kernfs_fop_write_iter
2025/12/22 08:42 upstream 765b233a9b94 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in kernfs_fop_write_iter
2025/12/02 23:57 upstream 4a26e7032d7d d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in kernfs_fop_write_iter
2025/10/24 00:27 upstream 43e9ad0c55a3 c0460fcd .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in kernfs_fop_write_iter
2025/10/01 22:44 upstream 50c19e20ed2e a1859138 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in kernfs_fop_write_iter
2025/09/06 04:47 upstream c8ed9b5c02a5 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in kernfs_fop_write_iter
2025/08/30 14:22 upstream fb679c832b64 807a3b61 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in kernfs_fop_write_iter
2025/07/31 07:43 upstream e8d780dcd957 f8f2b4da .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in kernfs_fop_write_iter
2025/07/19 08:13 upstream 4871b7cb27f4 7117feec .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in kernfs_fop_write_iter
2025/07/17 11:27 upstream e2291551827f 44f8051e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in kernfs_fop_write_iter
2025/07/17 03:05 upstream e2291551827f 44f8051e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in kernfs_fop_write_iter
2025/07/16 23:45 upstream 155a3c003e55 44f8051e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in kernfs_fop_write_iter
2025/07/16 16:29 upstream 155a3c003e55 c118d736 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in kernfs_fop_write_iter
2025/07/16 10:41 upstream 155a3c003e55 c118d736 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in kernfs_fop_write_iter
2025/07/16 05:38 upstream 155a3c003e55 03fcfc4b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in kernfs_fop_write_iter
2025/05/05 07:30 upstream 92a09c47464d b0714e37 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in kernfs_fop_write_iter
2025/11/09 05:16 upstream 7bb4d6512545 4e1406b4 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in kernfs_fop_write_iter
2025/10/24 09:27 upstream 6fab32bb6508 c0460fcd .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in kernfs_fop_write_iter
2025/08/24 13:41 upstream 8d245acc1e88 bf27483f .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in kernfs_fop_write_iter
2025/08/06 12:36 upstream a530a36bb548 4bd24a3e .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in kernfs_fop_write_iter
2025/07/13 05:03 upstream 3f31a806a62e 3cda49cf .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in kernfs_fop_write_iter
2024/10/10 06:48 upstream b983b271662b 0278d004 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in kernfs_fop_write_iter
2025/12/27 22:11 upstream c53f467229a7 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in kernfs_fop_write_iter
2025/12/26 05:42 upstream ccd1cdca5cd4 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in kernfs_fop_write_iter
2025/12/25 19:02 upstream ccd1cdca5cd4 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in kernfs_fop_write_iter
2025/12/25 17:09 upstream ccd1cdca5cd4 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in kernfs_fop_write_iter
2025/12/25 11:45 upstream ccd1cdca5cd4 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in kernfs_fop_write_iter
2025/12/24 13:49 upstream b927546677c8 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in kernfs_fop_write_iter
2025/12/22 06:20 upstream 765b233a9b94 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in kernfs_fop_write_iter
2025/11/08 07:24 upstream da32d155f4a8 4e1406b4 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in kernfs_fop_write_iter
2025/10/09 09:17 upstream cd5a0afbdf80 7e2882b3 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in kernfs_fop_write_iter
2025/07/19 12:15 upstream c7de79e662b8 7117feec .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in kernfs_fop_write_iter
2025/12/28 15:13 linux-next cc3aa43b44bd d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in kernfs_fop_write_iter
2025/12/27 12:33 linux-next cc3aa43b44bd d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in kernfs_fop_write_iter
2025/12/26 01:58 linux-next cc3aa43b44bd d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in kernfs_fop_write_iter
2025/12/23 13:21 linux-next cc3aa43b44bd d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in kernfs_fop_write_iter
2025/12/23 08:03 linux-next cc3aa43b44bd d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in kernfs_fop_write_iter
2025/12/23 01:26 linux-next cc3aa43b44bd d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in kernfs_fop_write_iter
2025/12/18 22:24 linux-next 1058ca9db0ed d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in kernfs_fop_write_iter
2025/09/06 13:37 linux-next be5d4872e528 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in kernfs_fop_write_iter
* Struck through repros no longer work on HEAD.