possible deadlock in anon_pipe_write (3)

Status: upstream: reported on 2026/08/15 00:11
Subsystems: autofs
Labels: prio:low
[Documentation on labels]
Reported-by: syzbot+c36cbd4737e4508de101@syzkaller.appspotmail.com
First crash: 98d, last: 4d12h
▶ ▼ ✨ AI Jobs (8)
ID Workflow Result Correct Bug Created Started Finished Revision
00a9e016 assessment-security DenialOfService: ✅ Exploitable: ❌ FilesystemTrigger: ❌ NetworkTrigger: ❌ PeripheralTrigger: ❌ RemoteTrigger: ❌ Unprivileged: ❌ UserNamespace: ❌ VMGuestTrigger: ❌ VMHostTrigger: ❌ ❓ possible deadlock in anon_pipe_write (3) 2026/10/15 00:02 2026/10/15 00:02 2026/10/15 00:44 8fb0ae89
5b08dc56 repro-c Reproduced: ✅ ❓ possible deadlock in anon_pipe_write (3) 2026/10/06 08:52 2026/10/06 08:52 2026/10/06 09:35 f7710056
05588fcb assessment-security 💥 possible deadlock in anon_pipe_write (3) 2026/09/14 01:00 2026/09/14 01:00 2026/09/14 01:00 70a60e12
8f1c8e57 assessment-security 💥 possible deadlock in anon_pipe_write (3) 2026/08/29 00:03 2026/08/29 00:03 2026/08/29 00:03 bcbc8ceb
29418e93 assessment-security 💥 possible deadlock in anon_pipe_write (3) 2026/08/20 00:58 2026/08/20 00:58 2026/08/20 00:58 1e72964b
98548aea assessment-security 💥 possible deadlock in anon_pipe_write (3) 2026/08/16 00:34 2026/08/16 00:34 2026/08/16 00:34 746171ee
69a57704 assessment-security 💥 possible deadlock in anon_pipe_write (3) 2026/08/14 00:17 2026/08/14 00:17 2026/08/14 00:17 0165196a
4fa59020 assessment-security 💥 possible deadlock in anon_pipe_write (3) 2026/08/12 03:31 2026/08/12 03:31 2026/08/12 03:31 f8d35649
▶ ▼ Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [autofs?] possible deadlock in anon_pipe_write (3) 0 (1) 2026/08/15 00:11
▶ ▼ Similar bugs (2)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in anon_pipe_write autofs 4 79 300d 556d 0/29 auto-obsoleted due to no activity on 2026/03/31 06:26
upstream possible deadlock in anon_pipe_write (2) prio:low autofs 4 1 217d 213d 0/29 auto-obsoleted due to no activity on 2026/07/22 15:37
▶ ▼ Last patch testing requests (1)
Created Duration User Patch Repo Result
2026/10/06 09:35 13m retest repro git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 2c3418fffa9d037b2038a6db48be63f9e2291806 error job log

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Tainted: G             L     
------------------------------------------------------
syz.4.2060/14559 is trying to acquire lock:
ffff88805c277060 (&pipe->mutex){+.+.}-{4:4}, at: anon_pipe_prefill_and_lock fs/pipe.c:165 [inline]
ffff88805c277060 (&pipe->mutex){+.+.}-{4:4}, at: anon_pipe_write+0x28f/0x1a90 fs/pipe.c:491

but task is already holding lock:
ffff88802adef138 (&sbi->pipe_mutex){+.+.}-{4:4}, at: autofs_write fs/autofs/waitq.c:68 [inline]
ffff88802adef138 (&sbi->pipe_mutex){+.+.}-{4:4}, at: autofs_notify_daemon+0x75d/0xf10 fs/autofs/waitq.c:177

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #3 (&sbi->pipe_mutex){+.+.}-{4:4}:
       __mutex_lock_common kernel/locking/mutex.c:646 [inline]
       __mutex_lock+0x197/0x15a0 kernel/locking/mutex.c:821
       autofs_write fs/autofs/waitq.c:68 [inline]
       autofs_notify_daemon+0x75d/0xf10 fs/autofs/waitq.c:177
       autofs_wait+0x11ad/0x18a0 fs/autofs/waitq.c:439
       autofs_mount_wait+0x16b/0x390 fs/autofs/root.c:256
       autofs_d_automount+0x64e/0x810 fs/autofs/root.c:410
       follow_automount fs/namei.c:1571 [inline]
       __traverse_mounts+0x2fe/0x5d0 fs/namei.c:1624
       traverse_mounts fs/namei.c:1653 [inline]
       handle_mounts fs/namei.c:1755 [inline]
       step_into_slowpath+0x4ba/0x820 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+0x433/0x8c0 fs/namei.c:2819
       filename_lookup+0x265/0x5d0 fs/namei.c:2848
       kern_path+0x3d/0x150 fs/namei.c:3042
       lookup_bdev+0xc8/0x2b0 block/bdev.c:1268
       resume_store+0x181/0x500 kernel/power/hibernate.c:1286
       kernfs_fop_write_iter+0x3a4/0x540 fs/kernfs/file.c:345
       new_sync_write fs/read_write.c:575 [inline]
       vfs_write+0x612/0xba0 fs/read_write.c:667
       ksys_write+0x150/0x270 fs/read_write.c:719
       do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
       do_syscall_64+0x16a/0x530 arch/x86/entry/syscall_64.c:89
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #2 (&of->mutex){+.+.}-{4:4}:
       __mutex_lock_common kernel/locking/mutex.c:646 [inline]
       __mutex_lock+0x197/0x15a0 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
       new_sync_read fs/read_write.c:473 [inline]
       vfs_read+0x595/0xa80 fs/read_write.c:554
       ksys_read+0x150/0x270 fs/read_write.c:696
       do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
       do_syscall_64+0x16a/0x530 arch/x86/entry/syscall_64.c:89
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #1 (&p->lock){+.+.}-{4:4}:
       __mutex_lock_common kernel/locking/mutex.c:646 [inline]
       __mutex_lock+0x197/0x15a0 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:293
       do_splice_read fs/splice.c:907 [inline]
       splice_file_to_pipe+0x4ab/0x720 fs/splice.c:1245
       do_splice+0x124f/0x1a60 fs/splice.c:1329
       __do_splice fs/splice.c:1386 [inline]
       __do_sys_splice fs/splice.c:1583 [inline]
       __se_sys_splice+0x353/0x490 fs/splice.c:1565
       do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
       do_syscall_64+0x16a/0x530 arch/x86/entry/syscall_64.c:89
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&pipe->mutex){+.+.}-{4:4}:
       check_prev_add kernel/locking/lockdep.c:3209 [inline]
       check_prevs_add kernel/locking/lockdep.c:3328 [inline]
       validate_chain kernel/locking/lockdep.c:3952 [inline]
       __lock_acquire+0x164c/0x2de0 kernel/locking/lockdep.c:5288
       lock_acquire+0x115/0x350 kernel/locking/lockdep.c:5942
       __mutex_lock_common kernel/locking/mutex.c:646 [inline]
       __mutex_lock+0x197/0x15a0 kernel/locking/mutex.c:821
       anon_pipe_prefill_and_lock fs/pipe.c:165 [inline]
       anon_pipe_write+0x28f/0x1a90 fs/pipe.c:491
       __kernel_write_iter+0x44a/0x8f0 fs/read_write.c:601
       __kernel_write+0x106/0x170 fs/read_write.c:621
       autofs_write fs/autofs/waitq.c:70 [inline]
       autofs_notify_daemon+0x770/0xf10 fs/autofs/waitq.c:177
       autofs_wait+0x11ad/0x18a0 fs/autofs/waitq.c:439
       autofs_mount_wait+0x16b/0x390 fs/autofs/root.c:256
       autofs_d_automount+0x64e/0x810 fs/autofs/root.c:410
       follow_automount fs/namei.c:1571 [inline]
       __traverse_mounts+0x2fe/0x5d0 fs/namei.c:1624
       traverse_mounts fs/namei.c:1653 [inline]
       handle_mounts fs/namei.c:1755 [inline]
       step_into_slowpath+0x4ba/0x820 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+0x433/0x8c0 fs/namei.c:2819
       filename_lookup+0x265/0x5d0 fs/namei.c:2848
       kern_path+0x3d/0x150 fs/namei.c:3042
       lookup_bdev+0xc8/0x2b0 block/bdev.c:1268
       resume_store+0x181/0x500 kernel/power/hibernate.c:1286
       kernfs_fop_write_iter+0x3a4/0x540 fs/kernfs/file.c:345
       new_sync_write fs/read_write.c:575 [inline]
       vfs_write+0x612/0xba0 fs/read_write.c:667
       ksys_write+0x150/0x270 fs/read_write.c:719
       do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
       do_syscall_64+0x16a/0x530 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:
  &pipe->mutex --> &of->mutex --> &sbi->pipe_mutex

 Possible unsafe locking scenario:

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

 *** DEADLOCK ***

locks held by syz.4.2060/14559: 5, on CPU#1:
 #0: ffff888061750470 (&f->f_pos_lock){+.+.}-{4:4}, at: fdget_pos+0x118/0x160 fs/file.c:1413
 #1: ffff888035ebc478 (sb_writers#7){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:2765 [inline]
 #1: ffff888035ebc478 (sb_writers#7){.+.+}-{0:0}, at: vfs_write+0x22b/0xba0 fs/read_write.c:663
 #2: ffff88807bf5d480 (&of->mutex){+.+.}-{4:4}, at: kernfs_fop_write_iter+0x1d8/0x540 fs/kernfs/file.c:336
 #3: ffff8880202faf08 (kn->active#86){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:73 [inline]
 #3: ffff8880202faf08 (kn->active#86){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x22b/0x540 fs/kernfs/file.c:337
 #4: ffff88802adef138 (&sbi->pipe_mutex){+.+.}-{4:4}, at: autofs_write fs/autofs/waitq.c:68 [inline]
 #4: ffff88802adef138 (&sbi->pipe_mutex){+.+.}-{4:4}, at: autofs_notify_daemon+0x75d/0xf10 fs/autofs/waitq.c:177

stack backtrace:
CPU: 1 UID: 0 PID: 14559 Comm: syz.4.2060 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_lvl+0xe8/0x150 lib/dump_stack.c:120
 print_circular_bug+0x2e2/0x300 kernel/locking/lockdep.c:2087
 check_noncircular+0x12f/0x150 kernel/locking/lockdep.c:2219
 check_prev_add kernel/locking/lockdep.c:3209 [inline]
 check_prevs_add kernel/locking/lockdep.c:3328 [inline]
 validate_chain kernel/locking/lockdep.c:3952 [inline]
 __lock_acquire+0x164c/0x2de0 kernel/locking/lockdep.c:5288
 lock_acquire+0x115/0x350 kernel/locking/lockdep.c:5942
 __mutex_lock_common kernel/locking/mutex.c:646 [inline]
 __mutex_lock+0x197/0x15a0 kernel/locking/mutex.c:821
 anon_pipe_prefill_and_lock fs/pipe.c:165 [inline]
 anon_pipe_write+0x28f/0x1a90 fs/pipe.c:491
 __kernel_write_iter+0x44a/0x8f0 fs/read_write.c:601
 __kernel_write+0x106/0x170 fs/read_write.c:621
 autofs_write fs/autofs/waitq.c:70 [inline]
 autofs_notify_daemon+0x770/0xf10 fs/autofs/waitq.c:177
 autofs_wait+0x11ad/0x18a0 fs/autofs/waitq.c:439
 autofs_mount_wait+0x16b/0x390 fs/autofs/root.c:256
 autofs_d_automount+0x64e/0x810 fs/autofs/root.c:410
 follow_automount fs/namei.c:1571 [inline]
 __traverse_mounts+0x2fe/0x5d0 fs/namei.c:1624
 traverse_mounts fs/namei.c:1653 [inline]
 handle_mounts fs/namei.c:1755 [inline]
 step_into_slowpath+0x4ba/0x820 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+0x433/0x8c0 fs/namei.c:2819
 filename_lookup+0x265/0x5d0 fs/namei.c:2848
 kern_path+0x3d/0x150 fs/namei.c:3042
 lookup_bdev+0xc8/0x2b0 block/bdev.c:1268
 resume_store+0x181/0x500 kernel/power/hibernate.c:1286
 kernfs_fop_write_iter+0x3a4/0x540 fs/kernfs/file.c:345
 new_sync_write fs/read_write.c:575 [inline]
 vfs_write+0x612/0xba0 fs/read_write.c:667
 ksys_write+0x150/0x270 fs/read_write.c:719
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x16a/0x530 arch/x86/entry/syscall_64.c:89
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fc0af3a94d9
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:00007fc0b02ec028 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fc0af625fa0 RCX: 00007fc0af3a94d9
RDX: 0000000000000012 RSI: 00002000000002c0 RDI: 0000000000000009
RBP: 00007fc0af43804e R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fc0af626038 R14: 00007fc0af625fa0 R15: 00007ffe24794c28
 </TASK>

Crashes (10):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/11/12 16:48 upstream 9d66f26fefac d6166547 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in anon_pipe_write
2026/11/12 16:48 upstream 9d66f26fefac d6166547 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in anon_pipe_write
2026/11/12 16:48 upstream 9d66f26fefac d6166547 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in anon_pipe_write
2026/11/10 09:44 upstream 7475ea8b5861 70ec0380 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in anon_pipe_write
2026/11/09 21:01 upstream 7475ea8b5861 5cecaf1f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in anon_pipe_write
2026/09/21 10:18 upstream 93f51579e7df 853b104b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in anon_pipe_write
2026/08/10 23:10 upstream d58772d8520c 508909ea .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in anon_pipe_write
2026/11/10 17:30 linux-next 630059a5a632 70ec0380 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in anon_pipe_write
2026/11/10 14:20 linux-next 630059a5a632 70ec0380 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in anon_pipe_write
2026/10/12 17:30 linux-next becb95e45ef0 745a967f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in anon_pipe_write
* Struck through repros no longer work on HEAD.