syzbot


possible deadlock in autofs_notify_daemon (2)

Status: upstream: reported on 2025/02/06 13:10
Subsystems: autofs
[Documentation on labels]
Reported-by: syzbot+8f1c85b6240c665f0c51@syzkaller.appspotmail.com
First crash: 165d, last: 19h28m
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [autofs?] possible deadlock in autofs_notify_daemon (2) 0 (1) 2025/02/06 13:10
Similar bugs (1)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in autofs_notify_daemon autofs 4 10 354d 361d 0/29 auto-obsoleted due to no activity on 2024/10/07 04:17

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
6.16.0-rc6-syzkaller-00037-ge2291551827f #0 Not tainted
------------------------------------------------------
syz.7.1423/12072 is trying to acquire lock:
ffff88805176b940 (&sbi->pipe_mutex){+.+.}-{4:4}, at: autofs_write fs/autofs/waitq.c:55 [inline]
ffff88805176b940 (&sbi->pipe_mutex){+.+.}-{4:4}, at: autofs_notify_daemon+0x735/0xe50 fs/autofs/waitq.c:164

but task is already holding lock:
ffff888068286c88 (&of->mutex){+.+.}-{4:4}, at: kernfs_fop_write_iter+0x1e0/0x4f0 fs/kernfs/file.c:325

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (&of->mutex){+.+.}-{4:4}:
       lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5871
       __mutex_lock_common kernel/locking/mutex.c:602 [inline]
       __mutex_lock+0x182/0xe80 kernel/locking/mutex.c:747
       kernfs_fop_write_iter+0x1e0/0x4f0 fs/kernfs/file.c:325
       iter_file_splice_write+0x937/0x1000 fs/splice.c:738
       do_splice_from fs/splice.c:935 [inline]
       do_splice+0xc79/0x1660 fs/splice.c:1348
       __do_splice fs/splice.c:1430 [inline]
       __do_sys_splice fs/splice.c:1633 [inline]
       __se_sys_splice+0x2e1/0x460 fs/splice.c:1615
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #1 (&pipe->mutex){+.+.}-{4:4}:
       lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5871
       __mutex_lock_common kernel/locking/mutex.c:602 [inline]
       __mutex_lock+0x182/0xe80 kernel/locking/mutex.c:747
       anon_pipe_write+0x16a/0x1360 fs/pipe.c:458
       __kernel_write_iter+0x3ec/0x860 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+0x748/0xe50 fs/autofs/waitq.c:164
       autofs_wait+0x11dc/0x1870 fs/autofs/waitq.c:426
       autofs_mount_wait+0x16b/0x330 fs/autofs/root.c:255
       autofs_d_automount+0x393/0x720 fs/autofs/root.c:401
       follow_automount fs/namei.c:1455 [inline]
       __traverse_mounts+0x308/0x5b0 fs/namei.c:1500
       traverse_mounts fs/namei.c:1529 [inline]
       handle_mounts fs/namei.c:1632 [inline]
       step_into+0x534/0xf30 fs/namei.c:1976
       walk_component fs/namei.c:2144 [inline]
       link_path_walk+0x77b/0xea0 fs/namei.c:2506
       path_lookupat+0x97/0x430 fs/namei.c:2662
       filename_lookup+0x212/0x570 fs/namei.c:2692
       user_path_at+0x3a/0x60 fs/namei.c:3136
       bpf_obj_do_get kernel/bpf/inode.c:503 [inline]
       bpf_obj_get_user+0xa9/0x430 kernel/bpf/inode.c:538
       __sys_bpf+0x71e/0x860 kernel/bpf/syscall.c:5842
       __do_sys_bpf kernel/bpf/syscall.c:5943 [inline]
       __se_sys_bpf kernel/bpf/syscall.c:5941 [inline]
       __x64_sys_bpf+0x7c/0x90 kernel/bpf/syscall.c:5941
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&sbi->pipe_mutex){+.+.}-{4:4}:
       check_prev_add kernel/locking/lockdep.c:3168 [inline]
       check_prevs_add kernel/locking/lockdep.c:3287 [inline]
       validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3911
       __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5240
       lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5871
       __mutex_lock_common kernel/locking/mutex.c:602 [inline]
       __mutex_lock+0x182/0xe80 kernel/locking/mutex.c:747
       autofs_write fs/autofs/waitq.c:55 [inline]
       autofs_notify_daemon+0x735/0xe50 fs/autofs/waitq.c:164
       autofs_wait+0x11dc/0x1870 fs/autofs/waitq.c:426
       autofs_mount_wait+0x16b/0x330 fs/autofs/root.c:255
       autofs_d_automount+0x393/0x720 fs/autofs/root.c:401
       follow_automount fs/namei.c:1455 [inline]
       __traverse_mounts+0x308/0x5b0 fs/namei.c:1500
       traverse_mounts fs/namei.c:1529 [inline]
       handle_mounts fs/namei.c:1632 [inline]
       step_into+0x534/0xf30 fs/namei.c:1976
       lookup_last fs/namei.c:2639 [inline]
       path_lookupat+0x163/0x430 fs/namei.c:2663
       filename_lookup+0x212/0x570 fs/namei.c:2692
       kern_path+0x35/0x50 fs/namei.c:2825
       lookup_bdev+0xc0/0x280 block/bdev.c:1205
       resume_store+0x169/0x460 kernel/power/hibernate.c:1269
       kernfs_fop_write_iter+0x378/0x4f0 fs/kernfs/file.c:334
       new_sync_write fs/read_write.c:593 [inline]
       vfs_write+0x54b/0xa90 fs/read_write.c:686
       ksys_write+0x145/0x250 fs/read_write.c:738
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xfa/0x3b0 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:
  &sbi->pipe_mutex --> &pipe->mutex --> &of->mutex

 Possible unsafe locking scenario:

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

 *** DEADLOCK ***

4 locks held by syz.7.1423/12072:
 #0: ffff8880309767f8 (&f->f_pos_lock){+.+.}-{4:4}, at: fdget_pos+0x247/0x320 fs/file.c:1217
 #1: ffff888030754428 (sb_writers#7){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:3096 [inline]
 #1: ffff888030754428 (sb_writers#7){.+.+}-{0:0}, at: vfs_write+0x211/0xa90 fs/read_write.c:682
 #2: ffff888068286c88 (&of->mutex){+.+.}-{4:4}, at: kernfs_fop_write_iter+0x1e0/0x4f0 fs/kernfs/file.c:325
 #3: ffff888140ade3c8 (kn->active#59){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x203/0x4f0 fs/kernfs/file.c:326

stack backtrace:
CPU: 1 UID: 0 PID: 12072 Comm: syz.7.1423 Not tainted 6.16.0-rc6-syzkaller-00037-ge2291551827f #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
 print_circular_bug+0x2ee/0x310 kernel/locking/lockdep.c:2046
 check_noncircular+0x134/0x160 kernel/locking/lockdep.c:2178
 check_prev_add kernel/locking/lockdep.c:3168 [inline]
 check_prevs_add kernel/locking/lockdep.c:3287 [inline]
 validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3911
 __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5240
 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5871
 __mutex_lock_common kernel/locking/mutex.c:602 [inline]
 __mutex_lock+0x182/0xe80 kernel/locking/mutex.c:747
 autofs_write fs/autofs/waitq.c:55 [inline]
 autofs_notify_daemon+0x735/0xe50 fs/autofs/waitq.c:164
 autofs_wait+0x11dc/0x1870 fs/autofs/waitq.c:426
 autofs_mount_wait+0x16b/0x330 fs/autofs/root.c:255
 autofs_d_automount+0x393/0x720 fs/autofs/root.c:401
 follow_automount fs/namei.c:1455 [inline]
 __traverse_mounts+0x308/0x5b0 fs/namei.c:1500
 traverse_mounts fs/namei.c:1529 [inline]
 handle_mounts fs/namei.c:1632 [inline]
 step_into+0x534/0xf30 fs/namei.c:1976
 lookup_last fs/namei.c:2639 [inline]
 path_lookupat+0x163/0x430 fs/namei.c:2663
 filename_lookup+0x212/0x570 fs/namei.c:2692
 kern_path+0x35/0x50 fs/namei.c:2825
 lookup_bdev+0xc0/0x280 block/bdev.c:1205
 resume_store+0x169/0x460 kernel/power/hibernate.c:1269
 kernfs_fop_write_iter+0x378/0x4f0 fs/kernfs/file.c:334
 new_sync_write fs/read_write.c:593 [inline]
 vfs_write+0x54b/0xa90 fs/read_write.c:686
 ksys_write+0x145/0x250 fs/read_write.c:738
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f5226d8e929
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:00007f5227b35038 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f5226fb6240 RCX: 00007f5226d8e929
RDX: 0000000000000012 RSI: 0000200000000040 RDI: 0000000000000009
RBP: 00007f5226e10ca1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f5226fb6240 R15: 00007fff5e6a5b08
 </TASK>
block device autoloading is deprecated and will be removed.
PM: Image not found (code -22)

Crashes (49):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
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 autofs_notify_daemon
2025/07/17 02:40 upstream e2291551827f 44f8051e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in autofs_notify_daemon
2025/07/16 23:22 upstream 155a3c003e55 44f8051e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in autofs_notify_daemon
2025/07/16 12:24 upstream 155a3c003e55 c118d736 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in autofs_notify_daemon
2025/07/16 10:19 upstream 155a3c003e55 c118d736 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in autofs_notify_daemon
2025/07/16 10:18 upstream 155a3c003e55 c118d736 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in autofs_notify_daemon
2025/07/16 10:17 upstream 155a3c003e55 c118d736 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in autofs_notify_daemon
2025/07/16 05:17 upstream 155a3c003e55 03fcfc4b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in autofs_notify_daemon
2025/07/16 05:16 upstream 155a3c003e55 03fcfc4b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in autofs_notify_daemon
2025/07/15 14:32 upstream 155a3c003e55 03fcfc4b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in autofs_notify_daemon
2025/07/15 14:32 upstream 155a3c003e55 03fcfc4b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in autofs_notify_daemon
2025/07/15 14:32 upstream 155a3c003e55 03fcfc4b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in autofs_notify_daemon
2025/07/15 14:32 upstream 155a3c003e55 03fcfc4b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in autofs_notify_daemon
2025/07/15 09:04 upstream 155a3c003e55 03fcfc4b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in autofs_notify_daemon
2025/07/15 08:51 upstream 155a3c003e55 03fcfc4b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in autofs_notify_daemon
2025/07/15 08:51 upstream 155a3c003e55 03fcfc4b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in autofs_notify_daemon
2025/07/15 07:53 upstream 155a3c003e55 03fcfc4b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in autofs_notify_daemon
2025/07/15 07:44 upstream 155a3c003e55 03fcfc4b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in autofs_notify_daemon
2025/07/15 07:44 upstream 155a3c003e55 03fcfc4b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in autofs_notify_daemon
2025/05/15 04:09 upstream 1a80a098c606 a4fa04ef .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in autofs_notify_daemon
2025/05/10 00:49 upstream 3013c33dcbd9 bb813bcc .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in autofs_notify_daemon
2025/05/07 19:45 upstream 707df3375124 350f4ffc .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in autofs_notify_daemon
2025/05/06 20:07 upstream 0d8d44db295c ae98e6b9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in autofs_notify_daemon
2025/05/06 17:56 upstream 01f95500a162 ae98e6b9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in autofs_notify_daemon
2025/05/06 15:42 upstream 01f95500a162 ae98e6b9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in autofs_notify_daemon
2025/05/04 23:41 upstream e8ab83e34bdc b0714e37 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in autofs_notify_daemon
2025/05/04 15:14 upstream e8ab83e34bdc b0714e37 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in autofs_notify_daemon
2025/04/30 08:23 upstream 8bac8898fe39 85a5a23f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in autofs_notify_daemon
2025/04/30 08:23 upstream 8bac8898fe39 85a5a23f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in autofs_notify_daemon
2025/04/24 13:50 upstream a79be02bba5c 9c80ffa0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in autofs_notify_daemon
2025/04/24 13:50 upstream a79be02bba5c 9c80ffa0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in autofs_notify_daemon
2025/04/21 12:44 upstream 9d7a0577c9db 2a20f901 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in autofs_notify_daemon
2025/04/21 07:34 upstream 9d7a0577c9db 2a20f901 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in autofs_notify_daemon
2025/04/21 07:34 upstream 9d7a0577c9db 2a20f901 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in autofs_notify_daemon
2025/04/20 18:09 upstream 6fea5fabd332 2a20f901 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in autofs_notify_daemon
2025/04/17 11:58 upstream cfb2e2c57aef 2a6ededb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in autofs_notify_daemon
2025/04/17 03:20 upstream c62f4b82d571 23b969b7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in autofs_notify_daemon
2025/02/02 22:41 upstream 69e858e0b8b2 568559e4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in autofs_notify_daemon
2025/02/02 13:03 upstream 69e858e0b8b2 568559e4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in autofs_notify_daemon
2025/05/14 20:57 upstream 9f35e33144ae a4fa04ef .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in autofs_notify_daemon
2025/05/12 09:19 upstream 82f2b0b97b36 77908e5f .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in autofs_notify_daemon
2025/05/08 15:23 upstream d76bb1ebb558 dbf35fa1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in autofs_notify_daemon
2025/02/04 07:29 upstream 0de63bb7d919 8f267cef .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in autofs_notify_daemon
2025/07/15 08:09 linux-next 0be23810e32e 03fcfc4b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in autofs_notify_daemon
2025/07/15 08:09 linux-next 0be23810e32e 03fcfc4b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in autofs_notify_daemon
* Struck through repros no longer work on HEAD.