syzbot


possible deadlock in seq_read_iter (4)

Status: closed as dup on 2024/05/27 09:33
Subsystems: autofs
[Documentation on labels]
Reported-by: syzbot+fcdd1f09adf0e00f70b1@syzkaller.appspotmail.com
First crash: 698d, last: 7d19h
Duplicate of
Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported
possible deadlock in kernfs_seq_start kernfs 4 C done error 38 14d 724d
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [overlayfs?] possible deadlock in seq_read_iter (4) 1 (2) 2024/05/27 09:33
Similar bugs (5)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 possible deadlock in seq_read_iter 4 84 50d 723d 0/3 upstream: reported on 2024/04/28 04:21
upstream possible deadlock in seq_read_iter (2) overlayfs 4 C done done 14 847d 1007d 25/29 fixed on 2024/02/02 10:05
upstream possible deadlock in seq_read_iter fs 4 2 1718d 1724d 0/29 auto-closed as invalid on 2021/12/05 03:01
upstream possible deadlock in seq_read_iter (3) overlayfs 4 148 709d 799d 25/29 fixed on 2024/05/23 00:16
linux-6.6 possible deadlock in seq_read_iter origin:upstream 4 syz error 12 118d 279d 0/2 upstream: reported syz repro on 2025/07/16 19:15

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Tainted: G             L     
------------------------------------------------------
syz.5.5060/27667 is trying to acquire lock:
ffff888049b70b08 (&p->lock){+.+.}-{4:4}, at: seq_read_iter+0xe1/0x1270 fs/seq_file.c:183

but task is already holding lock:
ffff888025e43068 (&pipe->mutex){+.+.}-{4:4}, at: pipe_lock fs/pipe.c:91 [inline]
ffff888025e43068 (&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:

-> #3 (&pipe->mutex){+.+.}-{4:4}:
       __mutex_lock_common kernel/locking/mutex.c:614 [inline]
       __mutex_lock+0x1a2/0x1b90 kernel/locking/mutex.c:776
       anon_pipe_write+0x163/0x1d40 fs/pipe.c:458
       __kernel_write_iter+0x6b2/0x920 fs/read_write.c:621
       __kernel_write+0xf6/0x140 fs/read_write.c:641
       autofs_write fs/autofs/waitq.c:57 [inline]
       autofs_notify_daemon+0x50d/0xd90 fs/autofs/waitq.c:164
       autofs_wait+0x10fd/0x1b50 fs/autofs/waitq.c:426
       autofs_mount_wait+0x132/0x3b0 fs/autofs/root.c:255
       autofs_d_automount+0x490/0x950 fs/autofs/root.c:409
       follow_automount fs/namei.c:1560 [inline]
       __traverse_mounts+0x1b9/0x8a0 fs/namei.c:1613
       traverse_mounts fs/namei.c:1642 [inline]
       handle_mounts fs/namei.c:1744 [inline]
       step_into_slowpath+0xb7e/0xf90 fs/namei.c:2100
       step_into fs/namei.c:2148 [inline]
       walk_component fs/namei.c:2284 [inline]
       lookup_last fs/namei.c:2785 [inline]
       path_lookupat+0x58b/0xc40 fs/namei.c:2809
       filename_lookup+0x202/0x590 fs/namei.c:2838
       vfs_statx+0xff/0x3f0 fs/stat.c:353
       vfs_fstatat fs/stat.c:373 [inline]
       vfs_lstat include/linux/fs.h:3200 [inline]
       __do_sys_newlstat+0xaa/0x130 fs/stat.c:524
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0x106/0xf80 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #2 (&sbi->pipe_mutex){+.+.}-{4:4}:
       __mutex_lock_common kernel/locking/mutex.c:614 [inline]
       __mutex_lock+0x1a2/0x1b90 kernel/locking/mutex.c:776
       autofs_write fs/autofs/waitq.c:55 [inline]
       autofs_notify_daemon+0x4f8/0xd90 fs/autofs/waitq.c:164
       autofs_wait+0x10fd/0x1b50 fs/autofs/waitq.c:426
       autofs_mount_wait+0x132/0x3b0 fs/autofs/root.c:255
       autofs_d_automount+0x490/0x950 fs/autofs/root.c:409
       follow_automount fs/namei.c:1560 [inline]
       __traverse_mounts+0x1b9/0x8a0 fs/namei.c:1613
       traverse_mounts fs/namei.c:1642 [inline]
       handle_mounts fs/namei.c:1744 [inline]
       step_into_slowpath+0xb7e/0xf90 fs/namei.c:2100
       step_into fs/namei.c:2148 [inline]
       walk_component fs/namei.c:2284 [inline]
       lookup_last fs/namei.c:2785 [inline]
       path_lookupat+0x58b/0xc40 fs/namei.c:2809
       filename_lookup+0x202/0x590 fs/namei.c:2838
       kern_path+0x37/0x50 fs/namei.c:3044
       lookup_bdev+0xd8/0x280 block/bdev.c:1221
       resume_store+0x1d6/0x460 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+0x3e0/0x5f0 fs/kernfs/file.c:352
       aio_write+0x3ba/0x920 fs/aio.c:1633
       __io_submit_one fs/aio.c:2005 [inline]
       io_submit_one+0x1142/0x1fb0 fs/aio.c:2052
       __do_sys_io_submit fs/aio.c:2111 [inline]
       __se_sys_io_submit fs/aio.c:2081 [inline]
       __x64_sys_io_submit+0x1b1/0x3a0 fs/aio.c:2081
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0x106/0xf80 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #1 (&of->mutex){+.+.}-{4:4}:
       __mutex_lock_common kernel/locking/mutex.c:614 [inline]
       __mutex_lock+0x1a2/0x1b90 kernel/locking/mutex.c:776
       kernfs_seq_start+0x4f/0x2a0 fs/kernfs/file.c:172
       seq_read_iter+0x2c1/0x1270 fs/seq_file.c:226
       kernfs_fop_read_iter+0x46c/0x610 fs/kernfs/file.c:297
       do_iter_readv_writev+0x60d/0x920 fs/read_write.c:827
       vfs_readv+0x4d3/0x8d0 fs/read_write.c:1020
       do_readv+0x13e/0x340 fs/read_write.c:1082
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0x106/0xf80 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&p->lock){+.+.}-{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+0x14b8/0x2630 kernel/locking/lockdep.c:5237
       lock_acquire kernel/locking/lockdep.c:5868 [inline]
       lock_acquire+0x1cf/0x380 kernel/locking/lockdep.c:5825
       __mutex_lock_common kernel/locking/mutex.c:614 [inline]
       __mutex_lock+0x1a2/0x1b90 kernel/locking/mutex.c:776
       seq_read_iter+0xe1/0x1270 fs/seq_file.c:183
       kernfs_fop_read_iter+0x46c/0x610 fs/kernfs/file.c:297
       copy_splice_read+0x4ba/0xb90 fs/splice.c:362
       do_splice_read fs/splice.c:980 [inline]
       do_splice_read+0x285/0x370 fs/splice.c:954
       splice_file_to_pipe+0x82/0x120 fs/splice.c:1290
       do_sendfile+0x366/0xe20 fs/read_write.c:1378
       __do_sys_sendfile64 fs/read_write.c:1433 [inline]
       __se_sys_sendfile64 fs/read_write.c:1419 [inline]
       __x64_sys_sendfile64+0x1d8/0x220 fs/read_write.c:1419
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0x106/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:
  &p->lock --> &sbi->pipe_mutex --> &pipe->mutex

 Possible unsafe locking scenario:

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

 *** DEADLOCK ***

1 lock held by syz.5.5060/27667:
 #0: ffff888025e43068 (&pipe->mutex){+.+.}-{4:4}, at: pipe_lock fs/pipe.c:91 [inline]
 #0: ffff888025e43068 (&pipe->mutex){+.+.}-{4:4}, at: pipe_lock+0x69/0x80 fs/pipe.c:88

stack backtrace:
CPU: 1 UID: 0 PID: 27667 Comm: syz.5.5060 Tainted: G             L      syzkaller #0 PREEMPT(full) 
Tainted: [L]=SOFTLOCKUP
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/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/0x1c7 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+0x14b8/0x2630 kernel/locking/lockdep.c:5237
 lock_acquire kernel/locking/lockdep.c:5868 [inline]
 lock_acquire+0x1cf/0x380 kernel/locking/lockdep.c:5825
 __mutex_lock_common kernel/locking/mutex.c:614 [inline]
 __mutex_lock+0x1a2/0x1b90 kernel/locking/mutex.c:776
 seq_read_iter+0xe1/0x1270 fs/seq_file.c:183
 kernfs_fop_read_iter+0x46c/0x610 fs/kernfs/file.c:297
 copy_splice_read+0x4ba/0xb90 fs/splice.c:362
 do_splice_read fs/splice.c:980 [inline]
 do_splice_read+0x285/0x370 fs/splice.c:954
 splice_file_to_pipe+0x82/0x120 fs/splice.c:1290
 do_sendfile+0x366/0xe20 fs/read_write.c:1378
 __do_sys_sendfile64 fs/read_write.c:1433 [inline]
 __se_sys_sendfile64 fs/read_write.c:1419 [inline]
 __x64_sys_sendfile64+0x1d8/0x220 fs/read_write.c:1419
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x106/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f57ccb9c819
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:00007f57cda76028 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 00007f57cce15fa0 RCX: 00007f57ccb9c819
RDX: 0000000000000000 RSI: 0000000000000006 RDI: 0000000000000004
RBP: 00007f57ccc32c91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f57cce16038 R14: 00007f57cce15fa0 R15: 00007ffecfc54348
 </TASK>

Crashes (244):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/04/13 23:57 upstream 0f0013213293 1a086e7c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in seq_read_iter
2026/03/19 22:28 upstream 8a30aeb0d1b4 bd6dcb30 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in seq_read_iter
2026/02/08 02:18 upstream e7aa57247700 4c131dc4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in seq_read_iter
2026/01/19 22:20 upstream 24d479d26b25 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in seq_read_iter
2025/12/22 20:29 upstream 9448598b22c5 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in seq_read_iter
2025/07/18 23:53 upstream d786aba32000 f550e092 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in seq_read_iter
2024/11/28 05:25 upstream aaf20f870da0 5df23865 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in seq_read_iter
2024/05/23 06:43 upstream b6394d6f7159 4d098039 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in seq_read_iter
2026/04/09 00:43 upstream 7f87a5ea75f0 d9b7f621 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/04/08 13:48 upstream 3036cd0d3328 d9b7f621 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/04/07 23:43 upstream 3036cd0d3328 2c961e87 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/04/06 18:12 upstream 591cd656a1bf 4440e7c2 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/04/04 08:47 upstream 631919fb12fe 4440e7c2 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/04/04 05:33 upstream 631919fb12fe 4440e7c2 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/04/03 13:46 upstream 5619b098e2fb 4440e7c2 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/03/27 06:03 upstream 46b513250491 4b3d9a38 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/03/24 21:51 upstream e3c33bc767b5 74e70d19 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/03/23 03:40 upstream 8d8bd2a5aa98 5b92003d .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/03/22 14:48 upstream 113ae7b4decc 5b92003d .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/03/14 21:43 upstream 267594792a71 ee8d34d6 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/03/13 22:49 upstream b36eb6e3f5d8 351cb5cf .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/03/12 14:38 upstream 80234b5ab240 4efadf07 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/03/11 10:11 upstream b4f0dd314b39 86914af9 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/03/05 22:21 upstream c107785c7e8d d20b04c8 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/03/04 04:16 upstream 0031c06807cf 4180d919 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/03/03 12:28 upstream af4e9ef3d784 28b83e23 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/03/02 22:02 upstream 11439c4635ed b9dd6534 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/02/28 15:56 upstream 4d349ee5c778 43249bac .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/02/27 04:26 upstream 3f4a08e64442 a2f13f71 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/02/25 02:50 upstream 7dff99b35460 787dfb7c .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/02/23 15:45 upstream 6de23f81a5e0 7c9658af .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/02/22 18:37 upstream 32a92f8c8932 6e7b5511 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/02/21 20:54 upstream d79526b89571 6e7b5511 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/02/21 10:42 upstream a95f71ad3e2e 6e7b5511 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/02/20 15:25 upstream 8bf22c33e7a1 741f5161 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/02/20 10:42 upstream 8bf22c33e7a1 17d780d6 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/02/17 21:33 upstream d295082ea672 4db8fa92 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/02/11 17:32 upstream 192c0159402e 75707236 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/02/09 02:57 upstream e98f34af6116 4c131dc4 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/02/04 15:19 upstream 5fd0a1df5d05 ea10c935 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/02/04 06:21 upstream de0674d9bc69 42b01fab .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/02/03 03:43 upstream dee65f79364c d78927dd .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/02/02 19:27 upstream 18f7fcd5e69a 018ebef2 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/01/31 05:52 upstream 283073725700 c75a2f6e .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/01/30 16:47 upstream 4d310797262f ea6dba22 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/01/30 05:53 upstream 4d310797262f bfa73b7b .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/01/29 13:07 upstream 8dfce8991b95 aeb6fdd5 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2026/04/10 18:19 upstream 9a9c8ce300cd 38c8e246 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in seq_read_iter
2026/04/04 09:57 upstream 631919fb12fe 4440e7c2 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in seq_read_iter
2026/03/26 08:15 upstream d2a43e7f89da c6143aac .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in seq_read_iter
2026/02/20 21:18 upstream 8bf22c33e7a1 741f5161 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in seq_read_iter
2026/02/16 23:47 upstream 0f2acd3148e0 84656fa6 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in seq_read_iter
2026/01/11 20:52 linux-next f417b7ffcbef d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in seq_read_iter
2025/10/08 17:09 linux-next 7c3ba4249a36 7e2882b3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in seq_read_iter
* Struck through repros no longer work on HEAD.