syzbot


possible deadlock in seq_read_iter (4)

Status: closed as dup on 2024/05/27 09:33
Subsystems: overlayfs autofs
[Documentation on labels]
Reported-by: syzbot+fcdd1f09adf0e00f70b1@syzkaller.appspotmail.com
First crash: 585d, last: 5h03m
Duplicate of
Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported
possible deadlock in kernfs_seq_start kernfs 4 C done error 33 17h52m 610d
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 79 4d09h 610d 0/3 upstream: reported on 2024/04/28 04:21
upstream possible deadlock in seq_read_iter (2) overlayfs 4 C done done 14 734d 893d 25/29 fixed on 2024/02/02 10:05
upstream possible deadlock in seq_read_iter fs 4 2 1605d 1611d 0/29 auto-closed as invalid on 2021/12/05 03:01
upstream possible deadlock in seq_read_iter (3) overlayfs 4 148 596d 685d 25/29 fixed on 2024/05/23 00:16
linux-6.6 possible deadlock in seq_read_iter origin:upstream 4 syz 12 4d16h 165d 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.7.4921/25852 is trying to acquire lock:
ffff888035d74418 (&p->lock){+.+.}-{4:4}, at: seq_read_iter+0xe1/0x12d0 fs/seq_file.c:182

but task is already holding lock:
ffff888079932068 (&pipe->mutex){+.+.}-{4:4}, at: pipe_lock fs/pipe.c:91 [inline]
ffff888079932068 (&pipe->mutex){+.+.}-{4:4}, at: pipe_lock+0x64/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+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:1499 [inline]
       __traverse_mounts+0x1b9/0x830 fs/namei.c:1552
       traverse_mounts fs/namei.c:1581 [inline]
       handle_mounts fs/namei.c:1686 [inline]
       step_into_slowpath+0x772/0xf50 fs/namei.c:2043
       step_into fs/namei.c:2091 [inline]
       walk_component fs/namei.c:2227 [inline]
       lookup_last fs/namei.c:2722 [inline]
       path_lookupat+0x627/0xc40 fs/namei.c:2746
       filename_lookup+0x224/0x5f0 fs/namei.c:2775
       user_path_at+0x3a/0x60 fs/namei.c:3567
       do_mount fs/namespace.c:4032 [inline]
       __do_sys_mount fs/namespace.c:4224 [inline]
       __se_sys_mount fs/namespace.c:4201 [inline]
       __x64_sys_mount+0x1fb/0x310 fs/namespace.c:4201
       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

-> #2 (&sbi->pipe_mutex){+.+.}-{4:4}:
       __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:1499 [inline]
       __traverse_mounts+0x1b9/0x830 fs/namei.c:1552
       traverse_mounts fs/namei.c:1581 [inline]
       handle_mounts fs/namei.c:1686 [inline]
       step_into_slowpath+0x772/0xf50 fs/namei.c:2043
       step_into fs/namei.c:2091 [inline]
       walk_component fs/namei.c:2227 [inline]
       lookup_last fs/namei.c:2722 [inline]
       path_lookupat+0x627/0xc40 fs/namei.c:2746
       filename_lookup+0x224/0x5f0 fs/namei.c:2775
       kern_path+0x35/0x50 fs/namei.c:2987
       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

-> #1 (&of->mutex){+.+.}-{4:4}:
       __mutex_lock_common kernel/locking/mutex.c:614 [inline]
       __mutex_lock+0x1aa/0x1ca0 kernel/locking/mutex.c:776
       kernfs_seq_start+0x4f/0x2a0 fs/kernfs/file.c:172
       seq_read_iter+0x2c1/0x12d0 fs/seq_file.c:225
       kernfs_fop_read_iter+0x46c/0x610 fs/kernfs/file.c:297
       copy_splice_read+0x618/0xc20 fs/splice.c:363
       do_splice_read fs/splice.c:982 [inline]
       do_splice_read+0x285/0x370 fs/splice.c:956
       splice_direct_to_actor+0x2a1/0xa30 fs/splice.c:1086
       do_splice_direct_actor fs/splice.c:1204 [inline]
       do_splice_direct+0x174/0x240 fs/splice.c:1230
       do_sendfile+0xb06/0xe50 fs/read_write.c:1370
       __do_sys_sendfile64 fs/read_write.c:1431 [inline]
       __se_sys_sendfile64 fs/read_write.c:1417 [inline]
       __x64_sys_sendfile64+0x1d8/0x220 fs/read_write.c:1417
       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 (&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+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
       seq_read_iter+0xe1/0x12d0 fs/seq_file.c:182
       kernfs_fop_read_iter+0x46c/0x610 fs/kernfs/file.c:297
       copy_splice_read+0x618/0xc20 fs/splice.c:363
       do_splice_read fs/splice.c:982 [inline]
       do_splice_read+0x285/0x370 fs/splice.c:956
       splice_file_to_pipe+0x109/0x120 fs/splice.c:1292
       do_sendfile+0x400/0xe50 fs/read_write.c:1376
       __do_sys_sendfile64 fs/read_write.c:1431 [inline]
       __se_sys_sendfile64 fs/read_write.c:1417 [inline]
       __x64_sys_sendfile64+0x1d8/0x220 fs/read_write.c:1417
       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:
  &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.7.4921/25852:
 #0: ffff888079932068 (&pipe->mutex){+.+.}-{4:4}, at: pipe_lock fs/pipe.c:91 [inline]
 #0: ffff888079932068 (&pipe->mutex){+.+.}-{4:4}, at: pipe_lock+0x64/0x80 fs/pipe.c:88

stack backtrace:
CPU: 1 UID: 0 PID: 25852 Comm: syz.7.4921 Tainted: G             L      syzkaller #0 PREEMPT(full) 
Tainted: [L]=SOFTLOCKUP
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
 seq_read_iter+0xe1/0x12d0 fs/seq_file.c:182
 kernfs_fop_read_iter+0x46c/0x610 fs/kernfs/file.c:297
 copy_splice_read+0x618/0xc20 fs/splice.c:363
 do_splice_read fs/splice.c:982 [inline]
 do_splice_read+0x285/0x370 fs/splice.c:956
 splice_file_to_pipe+0x109/0x120 fs/splice.c:1292
 do_sendfile+0x400/0xe50 fs/read_write.c:1376
 __do_sys_sendfile64 fs/read_write.c:1431 [inline]
 __se_sys_sendfile64 fs/read_write.c:1417 [inline]
 __x64_sys_sendfile64+0x1d8/0x220 fs/read_write.c:1417
 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:0x7fb80158f749
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:00007fb7ff7f6038 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 00007fb8017e5fa0 RCX: 00007fb80158f749
RDX: 0000000000000000 RSI: 0000000000000006 RDI: 0000000000000004
RBP: 00007fb801613f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fb8017e6038 R14: 00007fb8017e5fa0 R15: 00007ffe1afd9f58
 </TASK>

Crashes (141):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/12/28 14:50 upstream d26143bb38e2 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/28 00:21 upstream c53f467229a7 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/26 14:33 upstream ccd1cdca5cd4 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/26 08:14 upstream ccd1cdca5cd4 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/25 22:04 upstream ccd1cdca5cd4 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/25 18:17 upstream ccd1cdca5cd4 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/23 15:46 upstream b927546677c8 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/23 02:29 upstream 9448598b22c5 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/12/22 01:30 upstream 9094662f6707 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/19 09:41 upstream 516471569089 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/18 21:03 upstream ea1013c15392 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/05 11:21 upstream aa833fc394ba d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in seq_read_iter
2025/11/11 23:44 upstream 4427259cc7f7 4e1406b4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in seq_read_iter
2025/07/19 03:56 upstream d786aba32000 7117feec .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs 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
2025/12/22 14:34 upstream 9448598b22c5 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2025/12/22 11:52 upstream 765b233a9b94 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2025/11/25 14:00 upstream ac3fd01e4c1e 64219f15 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in seq_read_iter
2025/12/29 03:39 upstream c875a6c32467 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in seq_read_iter
2025/12/29 03:36 upstream c875a6c32467 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in seq_read_iter
2025/12/28 18:25 upstream d26143bb38e2 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in seq_read_iter
2025/12/28 12:17 upstream d26143bb38e2 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in seq_read_iter
2025/12/28 06:40 upstream d26143bb38e2 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in seq_read_iter
2025/12/27 19:03 upstream c53f467229a7 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in seq_read_iter
2025/12/27 04:22 upstream 3f0e9c8cefa9 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in seq_read_iter
2025/12/26 20:03 upstream ccd1cdca5cd4 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in seq_read_iter
2025/12/26 17:03 upstream ccd1cdca5cd4 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in seq_read_iter
2025/12/26 15:35 upstream ccd1cdca5cd4 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in seq_read_iter
2025/12/26 11:56 upstream ccd1cdca5cd4 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in seq_read_iter
2025/12/26 10:52 upstream ccd1cdca5cd4 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in seq_read_iter
2025/12/26 03:47 upstream ccd1cdca5cd4 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in seq_read_iter
2025/12/25 14:17 upstream ccd1cdca5cd4 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in seq_read_iter
2025/12/25 09:59 upstream ccd1cdca5cd4 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in seq_read_iter
2025/12/24 18:07 upstream b927546677c8 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in seq_read_iter
2025/12/24 13:46 upstream b927546677c8 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in seq_read_iter
2025/12/24 11:25 upstream b927546677c8 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in seq_read_iter
2025/12/24 08:05 upstream b927546677c8 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in seq_read_iter
2025/12/23 22:05 upstream b927546677c8 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in seq_read_iter
2025/12/23 13:19 upstream b927546677c8 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in seq_read_iter
2025/12/23 11:35 upstream b927546677c8 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in seq_read_iter
2025/12/22 05:27 upstream 765b233a9b94 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in seq_read_iter
2025/12/16 04:21 upstream 8f0b4cce4481 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in seq_read_iter
2025/12/15 02:49 upstream 8f0b4cce4481 d1b870e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in seq_read_iter
2025/11/09 20:32 upstream 439fc29dfd3b 4e1406b4 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in seq_read_iter
2025/11/07 06:04 upstream c2c2ccfd4ba7 4e1406b4 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in seq_read_iter
2025/11/06 12:58 upstream dc77806cf3b4 a6c9c731 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in seq_read_iter
2025/12/28 22:53 linux-next cc3aa43b44bd 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.