syzbot


possible deadlock in lookup_slow (3)

Status: upstream: reported on 2023/07/19 13:17
Subsystems: kernfs
[Documentation on labels]
Reported-by: syzbot+65459fd3b61877d717a3@syzkaller.appspotmail.com
First crash: 794d, last: 7h21m
Discussions (16)
Title Replies (including bot) Last reply
[syzbot] Monthly kernfs report (Aug 2025) 0 (1) 2025/08/23 16:32
[syzbot] Monthly kernfs report (Jul 2025) 0 (1) 2025/07/23 10:04
[syzbot] Monthly kernfs report (Jun 2025) 0 (1) 2025/06/23 07:33
[syzbot] Monthly kernfs report (May 2025) 0 (1) 2025/05/21 14:55
[syzbot] Monthly kernfs report (Mar 2025) 0 (1) 2025/03/19 21:29
[syzbot] Monthly kernfs report (Feb 2025) 0 (1) 2025/02/16 21:54
[syzbot] Monthly kernfs report (Jan 2025) 0 (1) 2025/01/16 10:12
[syzbot] Monthly kernfs report (Nov 2024) 0 (1) 2024/11/15 11:25
[syzbot] Monthly kernfs report (Jul 2024) 0 (1) 2024/07/09 14:10
[syzbot] Monthly kernfs report (May 2024) 0 (1) 2024/05/08 08:25
[syzbot] Monthly kernfs report (Apr 2024) 0 (1) 2024/04/08 08:30
[syzbot] Monthly kernfs report (Jan 2024) 0 (1) 2024/01/02 13:36
[syzbot] Monthly kernfs report (Nov 2023) 0 (1) 2023/11/29 13:03
[syzbot] Monthly kernfs report (Oct 2023) 0 (1) 2023/10/30 09:14
[syzbot] Monthly kernfs report (Sep 2023) 0 (1) 2023/09/28 14:01
[syzbot] [kernfs?] possible deadlock in lookup_slow (3) 0 (1) 2023/07/19 13:17
Similar bugs (8)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 possible deadlock in lookup_slow 4 11 745d 917d 0/3 auto-obsoleted due to no activity on 2023/12/11 13:10
linux-4.19 possible deadlock in lookup_slow 4 22 1920d 2346d 0/1 auto-closed as invalid on 2020/10/12 22:59
linux-6.1 possible deadlock in lookup_slow 4 1 228d 228d 0/3 auto-obsoleted due to no activity on 2025/05/11 18:32
upstream possible deadlock in lookup_slow fs 4 139 2306d 2547d 0/29 auto-closed as invalid on 2019/10/25 08:42
linux-6.1 possible deadlock in lookup_slow (2) 4 5 1h00m 123d 0/3 upstream: reported on 2025/05/16 17:47
linux-5.15 possible deadlock in lookup_slow (2) origin:lts-only 4 C 124 11d 643d 0/3 upstream: reported C repro on 2023/12/13 22:35
linux-4.14 possible deadlock in lookup_slow 4 C 2027 925d 2216d 0/1 upstream: reported C repro on 2019/08/24 01:53
upstream possible deadlock in lookup_slow (2) fs 4 7 2074d 2119d 0/29 auto-closed as invalid on 2020/05/11 09:17

Sample crash report:
netlink: 'syz.0.2484': attribute type 2 has an invalid length.
netlink: 12 bytes leftover after parsing attributes in process `syz.0.2484'.
netlink: 28 bytes leftover after parsing attributes in process `syz.0.2484'.
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.0.2484/15845 is trying to acquire lock:
ffff8880597ffad0 (&ovl_i_mutex_dir_key[depth]){++++}-{4:4}, at: inode_lock_shared include/linux/fs.h:885 [inline]
ffff8880597ffad0 (&ovl_i_mutex_dir_key[depth]){++++}-{4:4}, at: lookup_slow+0x46/0x70 fs/namei.c:1824

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

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #3 (&of->mutex){+.+.}-{4:4}:
       lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868
       __mutex_lock_common kernel/locking/mutex.c:598 [inline]
       __mutex_lock+0x187/0x1350 kernel/locking/mutex.c:760
       kernfs_fop_write_iter+0x1de/0x540 fs/kernfs/file.c:343
       iter_file_splice_write+0x975/0x10e0 fs/splice.c:738
       do_splice_from fs/splice.c:938 [inline]
       do_splice+0xc79/0x1660 fs/splice.c:1351
       __do_splice fs/splice.c:1433 [inline]
       __do_sys_splice fs/splice.c:1636 [inline]
       __se_sys_splice+0x2e1/0x460 fs/splice.c:1618
       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

-> #2 (&pipe->mutex){+.+.}-{4:4}:
       lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868
       __mutex_lock_common kernel/locking/mutex.c:598 [inline]
       __mutex_lock+0x187/0x1350 kernel/locking/mutex.c:760
       iter_file_splice_write+0x1e0/0x10e0 fs/splice.c:683
       do_splice_from fs/splice.c:938 [inline]
       do_splice+0xc79/0x1660 fs/splice.c:1351
       __do_splice fs/splice.c:1433 [inline]
       __do_sys_splice fs/splice.c:1636 [inline]
       __se_sys_splice+0x2e1/0x460 fs/splice.c:1618
       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 (sb_writers#5){.+.+}-{0:0}:
       lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868
       percpu_down_read_internal include/linux/percpu-rwsem.h:53 [inline]
       percpu_down_read_freezable include/linux/percpu-rwsem.h:83 [inline]
       __sb_start_write include/linux/fs.h:1799 [inline]
       sb_start_write+0x4d/0x1c0 include/linux/fs.h:1935
       mnt_want_write+0x41/0x90 fs/namespace.c:557
       ovl_create_object+0xfc/0x310 fs/overlayfs/dir.c:651
       lookup_open fs/namei.c:3708 [inline]
       open_last_lookups fs/namei.c:3807 [inline]
       path_openat+0x14f4/0x3830 fs/namei.c:4043
       do_filp_open+0x1fa/0x410 fs/namei.c:4073
       do_sys_openat2+0x121/0x1c0 fs/open.c:1435
       do_sys_open fs/open.c:1450 [inline]
       __do_sys_openat fs/open.c:1466 [inline]
       __se_sys_openat fs/open.c:1461 [inline]
       __x64_sys_openat+0x138/0x170 fs/open.c:1461
       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 (&ovl_i_mutex_dir_key[depth]){++++}-{4:4}:
       check_prev_add kernel/locking/lockdep.c:3165 [inline]
       check_prevs_add kernel/locking/lockdep.c:3284 [inline]
       validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3908
       __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5237
       lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868
       down_read+0x46/0x2e0 kernel/locking/rwsem.c:1537
       inode_lock_shared include/linux/fs.h:885 [inline]
       lookup_slow+0x46/0x70 fs/namei.c:1824
       walk_component+0x2d2/0x400 fs/namei.c:2129
       lookup_last fs/namei.c:2630 [inline]
       path_lookupat+0x163/0x430 fs/namei.c:2654
       filename_lookup+0x212/0x570 fs/namei.c:2683
       kern_path+0x35/0x50 fs/namei.c:2816
       lookup_bdev+0xc0/0x280 block/bdev.c:1205
       resume_store+0x169/0x460 kernel/power/hibernate.c:1296
       kernfs_fop_write_iter+0x3af/0x540 fs/kernfs/file.c:352
       new_sync_write fs/read_write.c:593 [inline]
       vfs_write+0x5c9/0xb30 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:
  &ovl_i_mutex_dir_key[depth] --> &pipe->mutex --> &of->mutex

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&of->mutex);
                               lock(&pipe->mutex);
                               lock(&of->mutex);
  rlock(&ovl_i_mutex_dir_key[depth]);

 *** DEADLOCK ***

4 locks held by syz.0.2484/15845:
 #0: ffff8880286a2d38 (&f->f_pos_lock){+.+.}-{4:4}, at: fdget_pos+0x247/0x320 fs/file.c:1232
 #1: ffff88802fcb4428 (sb_writers#7){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:3108 [inline]
 #1: ffff88802fcb4428 (sb_writers#7){.+.+}-{0:0}, at: vfs_write+0x211/0xb30 fs/read_write.c:682
 #2: ffff888055d29088 (&of->mutex){+.+.}-{4:4}, at: kernfs_fop_write_iter+0x1de/0x540 fs/kernfs/file.c:343
 #3: ffff888140ef22d8 (kn->active#62){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
 #3: ffff888140ef22d8 (kn->active#62){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x231/0x540 fs/kernfs/file.c:344

stack backtrace:
CPU: 0 UID: 0 PID: 15845 Comm: syz.0.2484 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
 print_circular_bug+0x2ee/0x310 kernel/locking/lockdep.c:2043
 check_noncircular+0x134/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+0xb9b/0x2140 kernel/locking/lockdep.c:3908
 __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5237
 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868
 down_read+0x46/0x2e0 kernel/locking/rwsem.c:1537
 inode_lock_shared include/linux/fs.h:885 [inline]
 lookup_slow+0x46/0x70 fs/namei.c:1824
 walk_component+0x2d2/0x400 fs/namei.c:2129
 lookup_last fs/namei.c:2630 [inline]
 path_lookupat+0x163/0x430 fs/namei.c:2654
 filename_lookup+0x212/0x570 fs/namei.c:2683
 kern_path+0x35/0x50 fs/namei.c:2816
 lookup_bdev+0xc0/0x280 block/bdev.c:1205
 resume_store+0x169/0x460 kernel/power/hibernate.c:1296
 kernfs_fop_write_iter+0x3af/0x540 fs/kernfs/file.c:352
 new_sync_write fs/read_write.c:593 [inline]
 vfs_write+0x5c9/0xb30 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:0x7f1f1998eba9
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:00007f1f1a832038 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f1f19bd5fa0 RCX: 00007f1f1998eba9
RDX: 0000000000000012 RSI: 0000200000000000 RDI: 0000000000000008
RBP: 00007f1f19a11e19 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f1f19bd6038 R14: 00007f1f19bd5fa0 R15: 00007ffe5ad6c118
 </TASK>
md: async del_gendisk mode will be removed in future, please upgrade to mdadm-4.5+
PM: Image not found (code -6)

Crashes (358):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/09/16 20:01 upstream 46a51f4f5eda e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in lookup_slow
2025/09/13 00:00 upstream 22f20375f5b7 e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2025/08/23 11:34 upstream 038d61fd6422 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in lookup_slow
2025/07/29 05:31 upstream ced1b9e0392d c4a95487 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in lookup_slow
2025/07/21 19:57 upstream 89be9a83ccf1 0b3788a0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in lookup_slow
2025/06/28 10:00 upstream 67a993863163 fc9d8ee5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2025/06/27 10:03 upstream f02769e7f272 803ce19b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2025/06/26 10:40 upstream ee88bddf7f2f 26d77996 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2025/06/21 11:10 upstream 11313e2f7812 d6cdfb8a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2025/06/20 22:17 upstream 41687a5c6f8b 804b3919 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2025/05/09 01:18 upstream d76bb1ebb558 dbf35fa1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in lookup_slow
2025/03/14 19:59 upstream 695caca9345a e2826670 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in lookup_slow
2025/02/13 18:18 upstream 4dc1d1bec898 2afad16e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in lookup_slow
2025/01/12 10:14 upstream b62cef9a5c67 6dbc6a9b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2025/01/07 21:00 upstream fbfd64d25c7a f3558dbf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in lookup_slow
2024/12/25 08:09 upstream 9b2ffa6148b1 444551c4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in lookup_slow
2024/12/23 06:03 upstream bcde95ce32b6 b4fbdbd4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in lookup_slow
2024/12/23 01:21 upstream bcde95ce32b6 b4fbdbd4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in lookup_slow
2024/12/17 12:39 upstream f44d154d6e3d f93b2b55 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in lookup_slow
2024/11/08 04:48 upstream 906bd684e4b1 c069283c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in lookup_slow
2024/11/07 14:24 upstream ff7afaeca1a1 c069283c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in lookup_slow
2024/11/06 21:43 upstream 7758b206117d df3dc63b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in lookup_slow
2024/11/04 02:39 upstream b9021de3ec2f f00eed24 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in lookup_slow
2024/11/03 03:17 upstream 11066801dd4b f00eed24 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in lookup_slow
2024/11/02 22:27 upstream 11066801dd4b f00eed24 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in lookup_slow
2024/11/02 16:11 upstream 11066801dd4b f00eed24 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in lookup_slow
2024/11/02 03:39 upstream 6c52d4da1c74 f00eed24 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in lookup_slow
2024/11/02 01:34 upstream 6c52d4da1c74 f00eed24 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in lookup_slow
2024/09/13 00:35 upstream fdf042df0463 60e1a995 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2024/09/06 14:27 upstream b831f83e40a2 464ac2ed .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2024/09/02 05:40 upstream c9f016e72b5c 1eda0d14 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2024/08/18 18:56 upstream c3f2d783a459 dbc93b08 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2024/07/18 00:45 upstream 51835949dda3 0f902625 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2024/06/29 08:06 upstream de0a9f448633 757f06b1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2024/06/23 08:57 upstream 563a50672d8a edc5149a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2024/06/15 08:30 upstream 2ccbdf43d5e7 f429ab00 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2024/06/10 03:27 upstream 83a7eefedc9b 82c05ab8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2024/06/10 02:04 upstream 771ed66105de 82c05ab8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2024/06/09 01:18 upstream 061d1af7b030 82c05ab8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2024/06/08 05:54 upstream 96e09b8f8166 82c05ab8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2024/06/06 18:38 upstream d30d0e49da71 121701b6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2024/06/04 23:12 upstream 2ab795141095 11f2afa5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2024/06/03 09:39 upstream c3f38fa61af7 0aba2352 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2024/06/03 05:22 upstream c3f38fa61af7 3113787f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2024/06/02 14:51 upstream 83814698cf48 3113787f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2024/06/02 00:55 upstream 89be4025b0db 3113787f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2024/06/02 00:55 upstream 89be4025b0db 3113787f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2024/06/01 11:47 upstream cc8ed4d0a848 3113787f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2024/05/31 22:27 upstream d8ec19857b09 3113787f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2023/07/19 08:57 upstream ccff6d117d8d 022df2bb .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2023/07/15 13:10 upstream b6e6cc1f78c7 35d9ecc5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2025/09/08 05:04 linux-next be5d4872e528 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in lookup_slow
2025/06/28 17:57 linux-next 2aeda9592360 fc9d8ee5 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in lookup_slow
2025/06/09 23:18 linux-next 475c850a7fdd 4826c28e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in lookup_slow
* Struck through repros no longer work on HEAD.