possible deadlock in kernfs_fop_write_iter (3)

Status: upstream: reported on 2026/07/07 14:24
Subsystems: autofs
Labels: prio:low
[Documentation on labels]
Reported-by: syzbot+c236d648c8a2fb8dd178@syzkaller.appspotmail.com
First crash: 136d, last: 3d10h
▶ ▼ ✨ AI Jobs (2)
ID Workflow Result Correct Bug Created Started Finished Revision
3ea1c037 repro-c Reproduced: ✅ ❓ possible deadlock in kernfs_fop_write_iter (3) 2026/10/12 16:02 2026/10/12 16:02 2026/10/12 16:46 745a967f
12665324 assessment-security DenialOfService: ❌ Exploitable: ❌ FilesystemTrigger: ❌ NetworkTrigger: ❌ PeripheralTrigger: ❌ RemoteTrigger: ❌ Unprivileged: ❌ UserNamespace: ❌ VMGuestTrigger: ❌ VMHostTrigger: ❌ ❓ possible deadlock in kernfs_fop_write_iter (3) 2026/07/05 08:02 2026/07/05 08:02 2026/07/05 08:55 93f57954
▶ ▼ Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [kernfs?] possible deadlock in kernfs_fop_write_iter (3) 0 (1) 2026/07/07 14:24
▶ ▼ Similar bugs (5)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in kernfs_fop_write_iter kernfs 4 14 842d 867d 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 445d 445d 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 647d 744d 0/3 auto-obsoleted due to no activity on 2025/05/17 20:05
upstream possible deadlock in kernfs_fop_write_iter (2) kernfs 4 139 252d 763d 0/29 auto-obsoleted due to no activity on 2026/05/17 16:33
linux-5.15 possible deadlock in kernfs_fop_write_iter (2) 4 1 533d 533d 0/3 auto-obsoleted due to no activity on 2025/09/09 09:34
▶ ▼ Last patch testing requests (1)
Created Duration User Patch Repo Result
2026/10/12 18:00 23m retest repro git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 24a19b953e2a3d0ea5a8c4951a0ab8f32720c907 report job log log

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Tainted: G             L     
------------------------------------------------------
syz.7.7101/31500 is trying to acquire lock:
ffff8880695cc480 (&of->mutex){+.+.}-{4:4}, at: kernfs_fop_write_iter+0x2c2/0x5f0 fs/kernfs/file.c:336

but task is already holding lock:
ffff888061b3fc60 (&pipe->mutex){+.+.}-{4:4}, at: pipe_lock fs/pipe.c:91 [inline]
ffff888061b3fc60 (&pipe->mutex){+.+.}-{4:4}, at: pipe_lock+0x69/0x80 fs/pipe.c:88

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (&pipe->mutex){+.+.}-{4:4}:
       lock_acquire kernel/locking/lockdep.c:5942 [inline]
       lock_acquire+0x1d1/0x380 kernel/locking/lockdep.c:5899
       __mutex_lock_common kernel/locking/mutex.c:646 [inline]
       __mutex_lock+0x19f/0x1c10 kernel/locking/mutex.c:821
       anon_pipe_prefill_and_lock+0x16c/0x580 fs/pipe.c:165
       anon_pipe_write+0x164/0x1bb0 fs/pipe.c:491
       __kernel_write_iter+0x6b2/0x920 fs/read_write.c:601
       __kernel_write+0xf6/0x140 fs/read_write.c:621
       autofs_write fs/autofs/waitq.c:70 [inline]
       autofs_notify_daemon+0x51e/0xe00 fs/autofs/waitq.c:177
       autofs_wait+0x10f8/0x1b30 fs/autofs/waitq.c:439
       autofs_mount_wait+0x132/0x3b0 fs/autofs/root.c:256
       autofs_d_automount+0x490/0x950 fs/autofs/root.c:410
       follow_automount fs/namei.c:1571 [inline]
       __traverse_mounts+0x1b9/0x8a0 fs/namei.c:1624
       traverse_mounts fs/namei.c:1653 [inline]
       handle_mounts fs/namei.c:1755 [inline]
       step_into_slowpath+0xb7e/0xf90 fs/namei.c:2110
       step_into fs/namei.c:2158 [inline]
       walk_component fs/namei.c:2294 [inline]
       lookup_last fs/namei.c:2795 [inline]
       path_lookupat+0x58b/0xc40 fs/namei.c:2819
       filename_lookup+0x202/0x590 fs/namei.c:2848
       user_statfs+0xb7/0x1a0 fs/statfs.c:104
       __do_sys_statfs+0x8d/0x100 fs/statfs.c:194
       do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
       do_syscall_64+0x123/0x7b0 arch/x86/entry/syscall_64.c:89
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #1 (&sbi->pipe_mutex){+.+.}-{4:4}:
       lock_acquire kernel/locking/lockdep.c:5942 [inline]
       lock_acquire+0x1d1/0x380 kernel/locking/lockdep.c:5899
       __mutex_lock_common kernel/locking/mutex.c:646 [inline]
       __mutex_lock+0x19f/0x1c10 kernel/locking/mutex.c:821
       autofs_write fs/autofs/waitq.c:68 [inline]
       autofs_notify_daemon+0x509/0xe00 fs/autofs/waitq.c:177
       autofs_wait+0x10f8/0x1b30 fs/autofs/waitq.c:439
       autofs_mount_wait+0x132/0x3b0 fs/autofs/root.c:256
       autofs_d_automount+0x490/0x950 fs/autofs/root.c:410
       follow_automount fs/namei.c:1571 [inline]
       __traverse_mounts+0x1b9/0x8a0 fs/namei.c:1624
       traverse_mounts fs/namei.c:1653 [inline]
       handle_mounts fs/namei.c:1755 [inline]
       step_into_slowpath+0xb7e/0xf90 fs/namei.c:2110
       step_into fs/namei.c:2158 [inline]
       walk_component fs/namei.c:2294 [inline]
       lookup_last fs/namei.c:2795 [inline]
       path_lookupat+0x58b/0xc40 fs/namei.c:2819
       filename_lookup+0x202/0x590 fs/namei.c:2848
       kern_path+0x37/0x50 fs/namei.c:3042
       lookup_bdev+0xd8/0x2a0 block/bdev.c:1268
       resume_store+0x1f5/0x480 kernel/power/hibernate.c:1286
       kobj_attr_store+0x58/0x80 lib/kobject.c:842
       sysfs_kf_write+0xf2/0x150 fs/sysfs/file.c:145
       kernfs_fop_write_iter+0x3e0/0x5f0 fs/kernfs/file.c:345
       new_sync_write fs/read_write.c:575 [inline]
       vfs_write+0x6af/0x1040 fs/read_write.c:667
       ksys_write+0x12a/0x250 fs/read_write.c:719
       do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
       do_syscall_64+0x123/0x7b0 arch/x86/entry/syscall_64.c:89
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&of->mutex){+.+.}-{4:4}:
       check_prev_add+0xeb/0xe60 kernel/locking/lockdep.c:3209
       check_prevs_add kernel/locking/lockdep.c:3328 [inline]
       validate_chain kernel/locking/lockdep.c:3952 [inline]
       __lock_acquire+0x1528/0x1f40 kernel/locking/lockdep.c:5288
       lock_acquire kernel/locking/lockdep.c:5942 [inline]
       lock_acquire+0x1d1/0x380 kernel/locking/lockdep.c:5899
       __mutex_lock_common kernel/locking/mutex.c:646 [inline]
       __mutex_lock+0x19f/0x1c10 kernel/locking/mutex.c:821
       kernfs_fop_write_iter+0x2c2/0x5f0 fs/kernfs/file.c:336
       iter_file_splice_write+0x836/0x1190 fs/splice.c:660
       do_splice_from fs/splice.c:863 [inline]
       do_splice+0x10a2/0x2090 fs/splice.c:1304
       __do_splice+0x33b/0x370 fs/splice.c:1386
       __do_sys_splice fs/splice.c:1583 [inline]
       __se_sys_splice fs/splice.c:1565 [inline]
       __x64_sys_splice+0x187/0x250 fs/splice.c:1565
       do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
       do_syscall_64+0x123/0x7b0 arch/x86/entry/syscall_64.c:89
       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 ***

locks held by syz.7.7101/31500: 2, on CPU#0:
 #0: ffff888075f1a478 (sb_writers#8){.+.+}-{0:0}, at: __do_splice+0x33b/0x370 fs/splice.c:1386
 #1: ffff888061b3fc60 (&pipe->mutex){+.+.}-{4:4}, at: pipe_lock fs/pipe.c:91 [inline]
 #1: ffff888061b3fc60 (&pipe->mutex){+.+.}-{4:4}, at: pipe_lock+0x69/0x80 fs/pipe.c:88

stack backtrace:
CPU: 0 UID: 0 PID: 31500 Comm: syz.7.7101 Tainted: G             L      syzkaller #0 PREEMPT(full) 
Tainted: [L]=SOFTLOCKUP
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/06/2026
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x100/0x190 lib/dump_stack.c:120
 print_circular_bug.cold+0x178/0x1be kernel/locking/lockdep.c:2087
 check_noncircular+0x146/0x160 kernel/locking/lockdep.c:2219
 check_prev_add+0xeb/0xe60 kernel/locking/lockdep.c:3209
 check_prevs_add kernel/locking/lockdep.c:3328 [inline]
 validate_chain kernel/locking/lockdep.c:3952 [inline]
 __lock_acquire+0x1528/0x1f40 kernel/locking/lockdep.c:5288
 lock_acquire kernel/locking/lockdep.c:5942 [inline]
 lock_acquire+0x1d1/0x380 kernel/locking/lockdep.c:5899
 __mutex_lock_common kernel/locking/mutex.c:646 [inline]
 __mutex_lock+0x19f/0x1c10 kernel/locking/mutex.c:821
 kernfs_fop_write_iter+0x2c2/0x5f0 fs/kernfs/file.c:336
 iter_file_splice_write+0x836/0x1190 fs/splice.c:660
 do_splice_from fs/splice.c:863 [inline]
 do_splice+0x10a2/0x2090 fs/splice.c:1304
 __do_splice+0x33b/0x370 fs/splice.c:1386
 __do_sys_splice fs/splice.c:1583 [inline]
 __se_sys_splice fs/splice.c:1565 [inline]
 __x64_sys_splice+0x187/0x250 fs/splice.c:1565
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x123/0x7b0 arch/x86/entry/syscall_64.c:89
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f1e5ffa94d9
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:00007f1e60dd9028 EFLAGS: 00000246 ORIG_RAX: 0000000000000113
RAX: ffffffffffffffda RBX: 00007f1e60226090 RCX: 00007f1e5ffa94d9
RDX: 0000000000000005 RSI: 0000000000000000 RDI: 0000000000000003
RBP: 00007f1e6003804e R08: 000000000004ffe6 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f1e60226128 R14: 00007f1e60226090 R15: 00007ffcfb878f18
 </TASK>

Crashes (38):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/11/13 04:27 upstream 7e1392a42ea2 26b2fee0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in kernfs_fop_write_iter
2026/11/06 18:40 upstream f66469d9905b 5cecaf1f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in kernfs_fop_write_iter
2026/11/05 19:07 upstream 05441d697f7f 5cecaf1f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in kernfs_fop_write_iter
2026/11/05 19:07 upstream 05441d697f7f 5cecaf1f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in kernfs_fop_write_iter
2026/09/23 21:21 upstream fe2ec83746e5 0a1606bc .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in kernfs_fop_write_iter
2026/09/23 20:50 upstream fe2ec83746e5 0a1606bc .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in kernfs_fop_write_iter
2026/09/23 19:07 upstream fe2ec83746e5 abce1216 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in kernfs_fop_write_iter
2026/09/23 10:40 upstream fe2ec83746e5 abce1216 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in kernfs_fop_write_iter
2026/09/23 10:40 upstream fe2ec83746e5 abce1216 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in kernfs_fop_write_iter
2026/09/23 10:39 upstream fe2ec83746e5 abce1216 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in kernfs_fop_write_iter
2026/09/23 09:12 upstream fe2ec83746e5 abce1216 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in kernfs_fop_write_iter
2026/09/23 09:12 upstream fe2ec83746e5 abce1216 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in kernfs_fop_write_iter
2026/09/23 09:00 upstream fe2ec83746e5 abce1216 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in kernfs_fop_write_iter
2026/09/21 13:46 upstream 93f51579e7df 853b104b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in kernfs_fop_write_iter
2026/09/21 10:48 upstream 93f51579e7df 853b104b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in kernfs_fop_write_iter
2026/09/21 10:48 upstream 93f51579e7df 853b104b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in kernfs_fop_write_iter
2026/09/21 10:47 upstream 93f51579e7df 853b104b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in kernfs_fop_write_iter
2026/09/19 00:22 upstream c3d85c669d09 8d7d05f1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in kernfs_fop_write_iter
2026/09/15 23:19 upstream f6e7b42bf05b 81a27d1a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in kernfs_fop_write_iter
2026/09/13 08:45 upstream cba2348ab114 70a60e12 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in kernfs_fop_write_iter
2026/09/06 13:12 upstream 1fc5a74b108f 4f7b22a0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in kernfs_fop_write_iter
2026/07/15 00:55 upstream 3b029c035b34 2130f682 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in kernfs_fop_write_iter
2026/07/14 22:59 upstream 3b029c035b34 2130f682 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in kernfs_fop_write_iter
2026/07/13 18:32 upstream a13c140cc289 a870962e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in kernfs_fop_write_iter
2026/07/03 14:12 upstream 87320be9f0d2 58bf2096 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in kernfs_fop_write_iter
2026/09/21 08:20 upstream 93f51579e7df 853b104b .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in kernfs_fop_write_iter
2026/09/21 08:19 upstream 93f51579e7df 853b104b .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in kernfs_fop_write_iter
2026/11/10 04:38 upstream 7475ea8b5861 bf7e1705 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in kernfs_fop_write_iter
2026/11/10 04:37 upstream 7475ea8b5861 bf7e1705 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in kernfs_fop_write_iter
2026/11/04 10:43 upstream 05441d697f7f 5af5b6c6 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in kernfs_fop_write_iter
2026/10/21 07:10 upstream 4cbdd58dfa7a 61c200c7 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in kernfs_fop_write_iter
2026/09/06 05:09 upstream 9f0346dcbea3 4f7b22a0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in kernfs_fop_write_iter
2026/09/06 05:08 upstream 9f0346dcbea3 4f7b22a0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in kernfs_fop_write_iter
2026/08/10 18:08 upstream db2ddb871435 558388e4 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in kernfs_fop_write_iter
2026/08/10 07:35 upstream db2ddb871435 5d63f80b .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in kernfs_fop_write_iter
2026/08/10 00:36 upstream b643e495ae92 5d63f80b .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in kernfs_fop_write_iter
2026/08/10 00:24 upstream b643e495ae92 5d63f80b .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in kernfs_fop_write_iter
2026/11/05 21:12 linux-next ddfe51b0a0f5 5cecaf1f .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.