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: 671d, last: 8d05h
Discussions (12)
Title Replies (including bot) Last reply
[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 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 possible deadlock in lookup_slow 11 622d 794d 0/3 auto-obsoleted due to no activity on 2023/12/11 13:10
linux-4.19 possible deadlock in lookup_slow 22 1797d 2223d 0/1 auto-closed as invalid on 2020/10/12 22:59
linux-6.1 possible deadlock in lookup_slow 1 105d 105d 0/3 auto-obsoleted due to no activity on 2025/05/11 18:32
upstream possible deadlock in lookup_slow fs 139 2183d 2424d 0/28 auto-closed as invalid on 2019/10/25 08:42
linux-6.1 possible deadlock in lookup_slow (2) 1 12h52m 12h51m 0/3 upstream: reported on 2025/05/16 17:47
linux-5.15 possible deadlock in lookup_slow (2) origin:lts-only C 89 3d00h 520d 0/3 upstream: reported C repro on 2023/12/13 22:35
linux-4.14 possible deadlock in lookup_slow C 2027 802d 2093d 0/1 upstream: reported C repro on 2019/08/24 01:53
upstream possible deadlock in lookup_slow (2) fs 7 1951d 1996d 0/28 auto-closed as invalid on 2020/05/11 09:17

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
6.15.0-rc5-syzkaller-00043-gd76bb1ebb558 #0 Not tainted
------------------------------------------------------
syz.2.4533/21669 is trying to acquire lock:
ffff88805b921888 (&ovl_i_mutex_dir_key[depth]){++++}-{4:4}, at: inode_lock_shared include/linux/fs.h:877 [inline]
ffff88805b921888 (&ovl_i_mutex_dir_key[depth]){++++}-{4:4}, at: lookup_slow+0x46/0x70 fs/namei.c:1833

but task is already holding lock:
ffff88802f779888 (&of->mutex){+.+.}-{4:4}, at: kernfs_fop_write_iter+0x1e0/0x4f0 fs/kernfs/file.c:325

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #4 (&of->mutex){+.+.}-{4:4}:
       lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5866
       __mutex_lock_common kernel/locking/mutex.c:601 [inline]
       __mutex_lock+0x182/0xe80 kernel/locking/mutex.c:746
       kernfs_seq_start+0x55/0x3c0 fs/kernfs/file.c:154
       traverse+0x15c/0x570 fs/seq_file.c:106
       seq_read_iter+0xcfe/0xe10 fs/seq_file.c:195
       do_iter_readv_writev+0x56b/0x7f0 fs/read_write.c:-1
       vfs_readv+0x257/0x840 fs/read_write.c:1016
       do_preadv fs/read_write.c:1130 [inline]
       __do_sys_preadv fs/read_write.c:1177 [inline]
       __se_sys_preadv fs/read_write.c:1172 [inline]
       __x64_sys_preadv+0x197/0x2a0 fs/read_write.c:1172
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xf6/0x210 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #3 (&p->lock){+.+.}-{4:4}:
       lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5866
       __mutex_lock_common kernel/locking/mutex.c:601 [inline]
       __mutex_lock+0x182/0xe80 kernel/locking/mutex.c:746
       seq_read_iter+0xb7/0xe10 fs/seq_file.c:182
       proc_reg_read_iter+0x1b4/0x280 fs/proc/inode.c:299
       copy_splice_read+0x54f/0x9b0 fs/splice.c:363
       do_splice_read fs/splice.c:979 [inline]
       splice_file_to_pipe+0x270/0x440 fs/splice.c:1289
       do_sendfile+0x475/0x7d0 fs/read_write.c:1374
       __do_sys_sendfile64 fs/read_write.c:1429 [inline]
       __se_sys_sendfile64+0x13e/0x190 fs/read_write.c:1415
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xf6/0x210 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:5866
       __mutex_lock_common kernel/locking/mutex.c:601 [inline]
       __mutex_lock+0x182/0xe80 kernel/locking/mutex.c:746
       iter_file_splice_write+0x1e6/0x1000 fs/splice.c:683
       do_splice_from fs/splice.c:935 [inline]
       do_splice+0xc76/0x1660 fs/splice.c:1348
       __do_splice fs/splice.c:1430 [inline]
       __do_sys_splice fs/splice.c:1633 [inline]
       __se_sys_splice+0x2e1/0x460 fs/splice.c:1615
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xf6/0x210 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:5866
       percpu_down_read include/linux/percpu-rwsem.h:52 [inline]
       __sb_start_write include/linux/fs.h:1783 [inline]
       sb_start_write+0x4d/0x1c0 include/linux/fs.h:1919
       mnt_want_write+0x41/0x90 fs/namespace.c:556
       ovl_create_object+0xfc/0x310 fs/overlayfs/dir.c:628
       lookup_open fs/namei.c:3701 [inline]
       open_last_lookups fs/namei.c:3800 [inline]
       path_openat+0x14f1/0x3830 fs/namei.c:4036
       do_filp_open+0x1fa/0x410 fs/namei.c:4066
       do_sys_openat2+0x121/0x1c0 fs/open.c:1429
       do_sys_open fs/open.c:1444 [inline]
       __do_sys_open fs/open.c:1452 [inline]
       __se_sys_open fs/open.c:1448 [inline]
       __x64_sys_open+0x11e/0x150 fs/open.c:1448
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xf6/0x210 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:3166 [inline]
       check_prevs_add kernel/locking/lockdep.c:3285 [inline]
       validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3909
       __lock_acquire+0xaac/0xd20 kernel/locking/lockdep.c:5235
       lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5866
       down_read+0x46/0x2e0 kernel/locking/rwsem.c:1524
       inode_lock_shared include/linux/fs.h:877 [inline]
       lookup_slow+0x46/0x70 fs/namei.c:1833
       walk_component+0x2d2/0x400 fs/namei.c:2138
       lookup_last fs/namei.c:2636 [inline]
       path_lookupat+0x163/0x430 fs/namei.c:2660
       filename_lookup+0x212/0x570 fs/namei.c:2689
       kern_path+0x35/0x50 fs/namei.c:2822
       lookup_bdev+0xc0/0x280 block/bdev.c:1205
       resume_store+0x169/0x460 kernel/power/hibernate.c:1248
       kernfs_fop_write_iter+0x375/0x4f0 fs/kernfs/file.c:334
       new_sync_write fs/read_write.c:591 [inline]
       vfs_write+0x548/0xa90 fs/read_write.c:684
       ksys_write+0x145/0x250 fs/read_write.c:736
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xf6/0x210 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] --> &p->lock --> &of->mutex

 Possible unsafe locking scenario:

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

 *** DEADLOCK ***

4 locks held by syz.2.4533/21669:
 #0: ffff888011894638 (&f->f_pos_lock){+.+.}-{4:4}, at: fdget_pos+0x247/0x320 fs/file.c:1213
 #1: ffff88803540a420 (sb_writers#7){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:3041 [inline]
 #1: ffff88803540a420 (sb_writers#7){.+.+}-{0:0}, at: vfs_write+0x211/0xa90 fs/read_write.c:680
 #2: ffff88802f779888 (&of->mutex){+.+.}-{4:4}, at: kernfs_fop_write_iter+0x1e0/0x4f0 fs/kernfs/file.c:325
 #3: ffff8881416854b8 (kn->active#66){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x203/0x4f0 fs/kernfs/file.c:326

stack backtrace:
CPU: 1 UID: 0 PID: 21669 Comm: syz.2.4533 Not tainted 6.15.0-rc5-syzkaller-00043-gd76bb1ebb558 #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/29/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
 print_circular_bug+0x2ee/0x310 kernel/locking/lockdep.c:2079
 check_noncircular+0x134/0x160 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+0xb9b/0x2140 kernel/locking/lockdep.c:3909
 __lock_acquire+0xaac/0xd20 kernel/locking/lockdep.c:5235
 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5866
 down_read+0x46/0x2e0 kernel/locking/rwsem.c:1524
 inode_lock_shared include/linux/fs.h:877 [inline]
 lookup_slow+0x46/0x70 fs/namei.c:1833
 walk_component+0x2d2/0x400 fs/namei.c:2138
 lookup_last fs/namei.c:2636 [inline]
 path_lookupat+0x163/0x430 fs/namei.c:2660
 filename_lookup+0x212/0x570 fs/namei.c:2689
 kern_path+0x35/0x50 fs/namei.c:2822
 lookup_bdev+0xc0/0x280 block/bdev.c:1205
 resume_store+0x169/0x460 kernel/power/hibernate.c:1248
 kernfs_fop_write_iter+0x375/0x4f0 fs/kernfs/file.c:334
 new_sync_write fs/read_write.c:591 [inline]
 vfs_write+0x548/0xa90 fs/read_write.c:684
 ksys_write+0x145/0x250 fs/read_write.c:736
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xf6/0x210 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f91c578e969
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:00007f91c660a038 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f91c59b6160 RCX: 00007f91c578e969
RDX: 0000000000000012 RSI: 0000200000000040 RDI: 000000000000000b
RBP: 00007f91c5810ab1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f91c59b6160 R15: 00007fff7e2fd5a8
 </TASK>
PM: Image not found (code -22)

Crashes (344):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
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
2024/05/31 20:11 upstream d8ec19857b09 0c378259 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2024/05/31 09:44 upstream 4a4be1ad3a6e 0c378259 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2024/05/28 19:47 upstream e0cce98fe279 34889ee3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2024/05/28 17:32 upstream 2bfcfd584ff5 34889ee3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2024/05/17 06:45 upstream 3c999d1ae3c7 c2e07261 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2024/05/17 02:37 upstream 3c999d1ae3c7 c2e07261 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2024/05/17 00:42 upstream 3c999d1ae3c7 c2e07261 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in lookup_slow
2024/05/09 17:34 upstream 45db3ab70092 05079661 .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
* Struck through repros no longer work on HEAD.