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: 126d, last: 25d
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 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in autofs_notify_daemon autofs 10 315d 322d 0/28 auto-obsoleted due to no activity on 2024/10/07 04:17

Sample crash report:
syzkaller0: entered promiscuous mode
syzkaller0: entered allmulticast mode
======================================================
WARNING: possible circular locking dependency detected
6.15.0-rc6-syzkaller-00080-g1a80a098c606 #0 Not tainted
------------------------------------------------------
syz.9.3419/19888 is trying to acquire lock:
ffff88807760b140 (&sbi->pipe_mutex){+.+.}-{4:4}, at: autofs_write fs/autofs/waitq.c:55 [inline]
ffff88807760b140 (&sbi->pipe_mutex){+.+.}-{4:4}, at: autofs_notify_daemon+0x4a6/0xd60 fs/autofs/waitq.c:164

but task is already holding lock:
ffff8880306a6088 (&of->mutex){+.+.}-{4:4}, at: kernfs_fop_write_iter+0x28f/0x510 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}:
       __mutex_lock_common kernel/locking/mutex.c:601 [inline]
       __mutex_lock+0x199/0xb90 kernel/locking/mutex.c:746
       kernfs_fop_write_iter+0x28f/0x510 fs/kernfs/file.c:325
       iter_file_splice_write+0x91f/0x1150 fs/splice.c:738
       do_splice_from fs/splice.c:935 [inline]
       do_splice+0x1478/0x1fc0 fs/splice.c:1348
       __do_splice+0x32a/0x360 fs/splice.c:1430
       __do_sys_splice fs/splice.c:1633 [inline]
       __se_sys_splice fs/splice.c:1615 [inline]
       __x64_sys_splice+0x187/0x250 fs/splice.c:1615
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xcd/0x260 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #1 (&pipe->mutex){+.+.}-{4:4}:
       __mutex_lock_common kernel/locking/mutex.c:601 [inline]
       __mutex_lock+0x199/0xb90 kernel/locking/mutex.c:746
       anon_pipe_write+0x15d/0x1a70 fs/pipe.c:459
       __kernel_write_iter+0x720/0xa90 fs/read_write.c:617
       __kernel_write+0xf5/0x140 fs/read_write.c:637
       autofs_write fs/autofs/waitq.c:57 [inline]
       autofs_notify_daemon+0x4db/0xd60 fs/autofs/waitq.c:164
       autofs_wait+0x10ca/0x1a70 fs/autofs/waitq.c:426
       autofs_mount_wait+0x132/0x380 fs/autofs/root.c:255
       autofs_d_automount+0x390/0x7f0 fs/autofs/root.c:401
       follow_automount fs/namei.c:1455 [inline]
       __traverse_mounts+0x192/0x790 fs/namei.c:1500
       traverse_mounts fs/namei.c:1529 [inline]
       handle_mounts fs/namei.c:1632 [inline]
       step_into+0x5aa/0x2270 fs/namei.c:1976
       open_last_lookups fs/namei.c:3827 [inline]
       path_openat+0x749/0x2d40 fs/namei.c:4036
       do_filp_open+0x20b/0x470 fs/namei.c:4066
       do_sys_openat2+0x11b/0x1d0 fs/open.c:1429
       do_sys_open fs/open.c:1444 [inline]
       __do_sys_openat fs/open.c:1460 [inline]
       __se_sys_openat fs/open.c:1455 [inline]
       __x64_sys_openat+0x174/0x210 fs/open.c:1455
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xcd/0x260 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:3166 [inline]
       check_prevs_add kernel/locking/lockdep.c:3285 [inline]
       validate_chain kernel/locking/lockdep.c:3909 [inline]
       __lock_acquire+0x1173/0x1ba0 kernel/locking/lockdep.c:5235
       lock_acquire kernel/locking/lockdep.c:5866 [inline]
       lock_acquire+0x179/0x350 kernel/locking/lockdep.c:5823
       __mutex_lock_common kernel/locking/mutex.c:601 [inline]
       __mutex_lock+0x199/0xb90 kernel/locking/mutex.c:746
       autofs_write fs/autofs/waitq.c:55 [inline]
       autofs_notify_daemon+0x4a6/0xd60 fs/autofs/waitq.c:164
       autofs_wait+0x10ca/0x1a70 fs/autofs/waitq.c:426
       autofs_mount_wait+0x132/0x380 fs/autofs/root.c:255
       autofs_d_automount+0x390/0x7f0 fs/autofs/root.c:401
       follow_automount fs/namei.c:1455 [inline]
       __traverse_mounts+0x192/0x790 fs/namei.c:1500
       traverse_mounts fs/namei.c:1529 [inline]
       handle_mounts fs/namei.c:1632 [inline]
       step_into+0x5aa/0x2270 fs/namei.c:1976
       walk_component+0xfc/0x5b0 fs/namei.c:2144
       lookup_last fs/namei.c:2636 [inline]
       path_lookupat+0x17e/0x780 fs/namei.c:2660
       filename_lookup+0x224/0x5f0 fs/namei.c:2689
       kern_path+0x35/0x50 fs/namei.c:2822
       lookup_bdev+0xd8/0x280 block/bdev.c:1205
       resume_store+0x1d6/0x460 kernel/power/hibernate.c:1248
       kobj_attr_store+0x55/0x80 lib/kobject.c:840
       sysfs_kf_write+0xef/0x150 fs/sysfs/file.c:145
       kernfs_fop_write_iter+0x351/0x510 fs/kernfs/file.c:334
       new_sync_write fs/read_write.c:591 [inline]
       vfs_write+0x5ba/0x1180 fs/read_write.c:684
       ksys_write+0x12a/0x240 fs/read_write.c:736
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xcd/0x260 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.9.3419/19888:
 #0: ffff88802ac335f8 (&f->f_pos_lock){+.+.}-{4:4}, at: fdget_pos+0x2a2/0x370 fs/file.c:1213
 #1: ffff888024c16420 (sb_writers#8){.+.+}-{0:0}, at: ksys_write+0x12a/0x240 fs/read_write.c:736
 #2: ffff8880306a6088 (&of->mutex){+.+.}-{4:4}, at: kernfs_fop_write_iter+0x28f/0x510 fs/kernfs/file.c:325
 #3: ffff888140ea3788 (kn->active#77){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x2b2/0x510 fs/kernfs/file.c:326

stack backtrace:
CPU: 0 UID: 0 PID: 19888 Comm: syz.9.3419 Not tainted 6.15.0-rc6-syzkaller-00080-g1a80a098c606 #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120
 print_circular_bug+0x275/0x350 kernel/locking/lockdep.c:2079
 check_noncircular+0x14c/0x170 kernel/locking/lockdep.c:2211
 check_prev_add kernel/locking/lockdep.c:3166 [inline]
 check_prevs_add kernel/locking/lockdep.c:3285 [inline]
 validate_chain kernel/locking/lockdep.c:3909 [inline]
 __lock_acquire+0x1173/0x1ba0 kernel/locking/lockdep.c:5235
 lock_acquire kernel/locking/lockdep.c:5866 [inline]
 lock_acquire+0x179/0x350 kernel/locking/lockdep.c:5823
 __mutex_lock_common kernel/locking/mutex.c:601 [inline]
 __mutex_lock+0x199/0xb90 kernel/locking/mutex.c:746
 autofs_write fs/autofs/waitq.c:55 [inline]
 autofs_notify_daemon+0x4a6/0xd60 fs/autofs/waitq.c:164
 autofs_wait+0x10ca/0x1a70 fs/autofs/waitq.c:426
 autofs_mount_wait+0x132/0x380 fs/autofs/root.c:255
 autofs_d_automount+0x390/0x7f0 fs/autofs/root.c:401
 follow_automount fs/namei.c:1455 [inline]
 __traverse_mounts+0x192/0x790 fs/namei.c:1500
 traverse_mounts fs/namei.c:1529 [inline]
 handle_mounts fs/namei.c:1632 [inline]
 step_into+0x5aa/0x2270 fs/namei.c:1976
 walk_component+0xfc/0x5b0 fs/namei.c:2144
 lookup_last fs/namei.c:2636 [inline]
 path_lookupat+0x17e/0x780 fs/namei.c:2660
 filename_lookup+0x224/0x5f0 fs/namei.c:2689
 kern_path+0x35/0x50 fs/namei.c:2822
 lookup_bdev+0xd8/0x280 block/bdev.c:1205
 resume_store+0x1d6/0x460 kernel/power/hibernate.c:1248
 kobj_attr_store+0x55/0x80 lib/kobject.c:840
 sysfs_kf_write+0xef/0x150 fs/sysfs/file.c:145
 kernfs_fop_write_iter+0x351/0x510 fs/kernfs/file.c:334
 new_sync_write fs/read_write.c:591 [inline]
 vfs_write+0x5ba/0x1180 fs/read_write.c:684
 ksys_write+0x12a/0x240 fs/read_write.c:736
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xcd/0x260 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f9e0ed8e969
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:00007f9e0fb65038 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f9e0efb5fa0 RCX: 00007f9e0ed8e969
RDX: 0000000000000012 RSI: 0000200000000000 RDI: 000000000000000a
RBP: 00007f9e0ee10ab1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f9e0efb5fa0 R15: 00007ffd7a5b1478
 </TASK>
PM: Image not found (code -6)

Crashes (24):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
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
* Struck through repros no longer work on HEAD.