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: 362d, last: 15d
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 550d 558d 0/29 auto-obsoleted due to no activity on 2024/10/07 04:17

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.3.972/10481 is trying to acquire lock:
ffff8880216e5948 (&sbi->pipe_mutex){+.+.}-{4:4}, at: autofs_write fs/autofs/waitq.c:55 [inline]
ffff8880216e5948 (&sbi->pipe_mutex){+.+.}-{4:4}, at: autofs_notify_daemon+0x4a6/0xd60 fs/autofs/waitq.c:164

but task is already holding lock:
ffff888027b49888 (&of->mutex){+.+.}-{4:4}, at: kernfs_fop_write_iter+0x28f/0x570 fs/kernfs/file.c:343

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:614 [inline]
       __mutex_lock+0x1aa/0x1ca0 kernel/locking/mutex.c:776
       kernfs_fop_write_iter+0x28f/0x570 fs/kernfs/file.c:343
       iter_file_splice_write+0xa24/0x12b0 fs/splice.c:738
       do_splice_from fs/splice.c:938 [inline]
       do_splice+0x1478/0x1fc0 fs/splice.c:1351
       __do_splice+0x32a/0x360 fs/splice.c:1433
       __do_sys_splice fs/splice.c:1636 [inline]
       __se_sys_splice fs/splice.c:1618 [inline]
       __x64_sys_splice+0x187/0x250 fs/splice.c:1618
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xcd/0xf80 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:614 [inline]
       __mutex_lock+0x1aa/0x1ca0 kernel/locking/mutex.c:776
       anon_pipe_write+0x15d/0x1bd0 fs/pipe.c:458
       __kernel_write_iter+0x720/0xb10 fs/read_write.c:619
       __kernel_write+0xf5/0x140 fs/read_write.c:639
       autofs_write fs/autofs/waitq.c:57 [inline]
       autofs_notify_daemon+0x4db/0xd60 fs/autofs/waitq.c:164
       autofs_wait+0x10f3/0x1ac0 fs/autofs/waitq.c:426
       autofs_mount_wait+0x132/0x3c0 fs/autofs/root.c:255
       autofs_d_automount+0x4b2/0x960 fs/autofs/root.c:409
       follow_automount fs/namei.c:1507 [inline]
       __traverse_mounts+0x1b9/0x830 fs/namei.c:1560
       traverse_mounts fs/namei.c:1589 [inline]
       handle_mounts fs/namei.c:1694 [inline]
       step_into_slowpath+0x772/0xf50 fs/namei.c:2051
       step_into fs/namei.c:2099 [inline]
       open_last_lookups fs/namei.c:4584 [inline]
       path_openat+0x10db/0x3140 fs/namei.c:4793
       do_filp_open+0x20b/0x470 fs/namei.c:4823
       do_sys_openat2+0x121/0x290 fs/open.c:1430
       do_sys_open fs/open.c:1436 [inline]
       __do_sys_openat fs/open.c:1452 [inline]
       __se_sys_openat fs/open.c:1447 [inline]
       __x64_sys_openat+0x174/0x210 fs/open.c:1447
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xcd/0xf80 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:3165 [inline]
       check_prevs_add kernel/locking/lockdep.c:3284 [inline]
       validate_chain kernel/locking/lockdep.c:3908 [inline]
       __lock_acquire+0x1669/0x2890 kernel/locking/lockdep.c:5237
       lock_acquire kernel/locking/lockdep.c:5868 [inline]
       lock_acquire+0x179/0x330 kernel/locking/lockdep.c:5825
       __mutex_lock_common kernel/locking/mutex.c:614 [inline]
       __mutex_lock+0x1aa/0x1ca0 kernel/locking/mutex.c:776
       autofs_write fs/autofs/waitq.c:55 [inline]
       autofs_notify_daemon+0x4a6/0xd60 fs/autofs/waitq.c:164
       autofs_wait+0x10f3/0x1ac0 fs/autofs/waitq.c:426
       autofs_mount_wait+0x132/0x3c0 fs/autofs/root.c:255
       autofs_d_automount+0x4b2/0x960 fs/autofs/root.c:409
       follow_automount fs/namei.c:1507 [inline]
       __traverse_mounts+0x1b9/0x830 fs/namei.c:1560
       traverse_mounts fs/namei.c:1589 [inline]
       handle_mounts fs/namei.c:1694 [inline]
       step_into_slowpath+0x772/0xf50 fs/namei.c:2051
       step_into fs/namei.c:2099 [inline]
       walk_component fs/namei.c:2235 [inline]
       lookup_last fs/namei.c:2730 [inline]
       path_lookupat+0x627/0xc40 fs/namei.c:2754
       filename_lookup+0x224/0x5f0 fs/namei.c:2783
       kern_path+0x35/0x50 fs/namei.c:2996
       lookup_bdev+0xd8/0x280 block/bdev.c:1222
       resume_store+0x1d6/0x490 kernel/power/hibernate.c:1306
       kobj_attr_store+0x58/0x80 lib/kobject.c:840
       sysfs_kf_write+0xf2/0x150 fs/sysfs/file.c:142
       kernfs_fop_write_iter+0x3af/0x570 fs/kernfs/file.c:352
       new_sync_write fs/read_write.c:593 [inline]
       vfs_write+0x7d3/0x11d0 fs/read_write.c:686
       ksys_write+0x12a/0x250 fs/read_write.c:738
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xcd/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:
  &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.3.972/10481:
 #0: ffff8880616470b8 (&f->f_pos_lock){+.+.}-{4:4}, at: fdget_pos+0x2a2/0x370 fs/file.c:1255
 #1: ffff88803393a420 (sb_writers#7){.+.+}-{0:0}, at: ksys_write+0x12a/0x250 fs/read_write.c:738
 #2: ffff888027b49888 (&of->mutex){+.+.}-{4:4}, at: kernfs_fop_write_iter+0x28f/0x570 fs/kernfs/file.c:343
 #3: ffff8881416ef008 (kn->active#63){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
 #3: ffff8881416ef008 (kn->active#63){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x2ff/0x570 fs/kernfs/file.c:344

stack backtrace:
CPU: 1 UID: 0 PID: 10481 Comm: syz.3.972 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/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/0x340 kernel/locking/lockdep.c:2043
 check_noncircular+0x146/0x160 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+0x1669/0x2890 kernel/locking/lockdep.c:5237
 lock_acquire kernel/locking/lockdep.c:5868 [inline]
 lock_acquire+0x179/0x330 kernel/locking/lockdep.c:5825
 __mutex_lock_common kernel/locking/mutex.c:614 [inline]
 __mutex_lock+0x1aa/0x1ca0 kernel/locking/mutex.c:776
 autofs_write fs/autofs/waitq.c:55 [inline]
 autofs_notify_daemon+0x4a6/0xd60 fs/autofs/waitq.c:164
 autofs_wait+0x10f3/0x1ac0 fs/autofs/waitq.c:426
 autofs_mount_wait+0x132/0x3c0 fs/autofs/root.c:255
 autofs_d_automount+0x4b2/0x960 fs/autofs/root.c:409
 follow_automount fs/namei.c:1507 [inline]
 __traverse_mounts+0x1b9/0x830 fs/namei.c:1560
 traverse_mounts fs/namei.c:1589 [inline]
 handle_mounts fs/namei.c:1694 [inline]
 step_into_slowpath+0x772/0xf50 fs/namei.c:2051
 step_into fs/namei.c:2099 [inline]
 walk_component fs/namei.c:2235 [inline]
 lookup_last fs/namei.c:2730 [inline]
 path_lookupat+0x627/0xc40 fs/namei.c:2754
 filename_lookup+0x224/0x5f0 fs/namei.c:2783
 kern_path+0x35/0x50 fs/namei.c:2996
 lookup_bdev+0xd8/0x280 block/bdev.c:1222
 resume_store+0x1d6/0x490 kernel/power/hibernate.c:1306
 kobj_attr_store+0x58/0x80 lib/kobject.c:840
 sysfs_kf_write+0xf2/0x150 fs/sysfs/file.c:142
 kernfs_fop_write_iter+0x3af/0x570 fs/kernfs/file.c:352
 new_sync_write fs/read_write.c:593 [inline]
 vfs_write+0x7d3/0x11d0 fs/read_write.c:686
 ksys_write+0x12a/0x250 fs/read_write.c:738
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xcd/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fad0338f749
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:00007fad04176038 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fad035e5fa0 RCX: 00007fad0338f749
RDX: 0000000000000012 RSI: 0000200000000040 RDI: 0000000000000003
RBP: 00007fad03413f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fad035e6038 R14: 00007fad035e5fa0 R15: 00007ffddeee3988
 </TASK>
PM: Image not found (code -22)

Crashes (167):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/01/13 11:19 upstream b71e635feefc d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in autofs_notify_daemon
2026/01/02 11:45 upstream b69053dd3ffb d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in autofs_notify_daemon
2026/01/02 03:07 upstream b69053dd3ffb d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in autofs_notify_daemon
2025/12/30 22:04 upstream dbf8fe85a16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in autofs_notify_daemon
2025/12/30 20:45 upstream dbf8fe85a16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in autofs_notify_daemon
2025/12/30 00:33 upstream 8640b74557fc d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in autofs_notify_daemon
2025/12/29 03:37 upstream c875a6c32467 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in autofs_notify_daemon
2025/12/28 03:55 upstream d26143bb38e2 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in autofs_notify_daemon
2025/12/27 12:22 upstream 3f0e9c8cefa9 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in autofs_notify_daemon
2025/12/27 02:21 upstream 3f0e9c8cefa9 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in autofs_notify_daemon
2025/12/26 20:22 upstream ccd1cdca5cd4 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in autofs_notify_daemon
2025/12/26 18:34 upstream ccd1cdca5cd4 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in autofs_notify_daemon
2025/12/26 00:42 upstream ccd1cdca5cd4 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in autofs_notify_daemon
2025/12/25 19:43 upstream ccd1cdca5cd4 d6526ea3 .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/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/12/20 17:28 upstream dd9b004b7ff3 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in autofs_notify_daemon
2026/01/15 00:01 upstream 944aacb68baf d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in autofs_notify_daemon
2026/01/13 14:32 upstream b71e635feefc d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in autofs_notify_daemon
2026/01/13 03:45 upstream b71e635feefc d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in autofs_notify_daemon
2026/01/12 23:30 upstream 0f61b1860cc3 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in autofs_notify_daemon
2026/01/12 23:23 upstream 0f61b1860cc3 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in autofs_notify_daemon
2026/01/08 10:02 upstream f0b9d8eb98df d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in autofs_notify_daemon
2026/01/03 20:37 upstream 805f9a061372 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in autofs_notify_daemon
2026/01/02 22:29 upstream 9b0436804460 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in autofs_notify_daemon
2026/01/02 21:02 upstream 9b0436804460 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in autofs_notify_daemon
2026/01/02 19:51 upstream 9b0436804460 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in autofs_notify_daemon
2026/01/02 06:23 upstream b69053dd3ffb d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in autofs_notify_daemon
2026/01/01 12:39 upstream b69053dd3ffb d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in autofs_notify_daemon
2026/01/01 10:03 upstream 349bd28a86f2 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in autofs_notify_daemon
2026/01/01 07:10 upstream 349bd28a86f2 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in autofs_notify_daemon
2026/01/01 04:05 upstream 349bd28a86f2 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in autofs_notify_daemon
2025/12/31 22:59 upstream 349bd28a86f2 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in autofs_notify_daemon
2025/12/30 15:23 upstream 8640b74557fc d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in autofs_notify_daemon
2025/12/30 09:30 upstream 8640b74557fc d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in autofs_notify_daemon
2025/12/29 20:34 upstream 7839932417dd d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in autofs_notify_daemon
2025/12/29 18:46 upstream 7839932417dd d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in autofs_notify_daemon
2025/12/29 11:17 upstream 7839932417dd d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in autofs_notify_daemon
2025/12/29 06:11 upstream c875a6c32467 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in autofs_notify_daemon
2025/12/29 04:52 upstream c875a6c32467 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in autofs_notify_daemon
2025/12/28 18:44 upstream d26143bb38e2 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in autofs_notify_daemon
2025/12/28 18:13 upstream d26143bb38e2 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in autofs_notify_daemon
2025/12/28 14:41 upstream d26143bb38e2 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in autofs_notify_daemon
2025/12/28 13:31 upstream d26143bb38e2 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in autofs_notify_daemon
2025/12/26 10:43 upstream ccd1cdca5cd4 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in autofs_notify_daemon
2025/12/26 09:22 upstream ccd1cdca5cd4 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in autofs_notify_daemon
2025/12/25 14:12 upstream ccd1cdca5cd4 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in autofs_notify_daemon
2026/01/15 04:17 linux-next b775e489bec7 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in autofs_notify_daemon
2026/01/11 21:22 linux-next f417b7ffcbef d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in autofs_notify_daemon
2026/01/03 10:42 linux-next cc3aa43b44bd d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in autofs_notify_daemon
2026/01/02 04:20 linux-next cc3aa43b44bd d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in autofs_notify_daemon
2026/01/01 05:51 linux-next cc3aa43b44bd d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in autofs_notify_daemon
2025/12/31 10:32 linux-next cc3aa43b44bd d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in autofs_notify_daemon
2025/12/27 01:01 linux-next cc3aa43b44bd d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in autofs_notify_daemon
2025/12/25 06:58 linux-next cc3aa43b44bd d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in autofs_notify_daemon
* Struck through repros no longer work on HEAD.