Title | Replies (including bot) | Last reply |
---|---|---|
[syzbot] [kernfs?] possible deadlock in walk_component (4) | 0 (1) | 2024/08/18 22:16 |
syzbot |
sign-in | mailing list | source | docs |
Title | Replies (including bot) | Last reply |
---|---|---|
[syzbot] [kernfs?] possible deadlock in walk_component (4) | 0 (1) | 2024/08/18 22:16 |
Kernel | Title | Repro | Cause bisect | Fix bisect | Count | Last | Reported | Patched | Status |
---|---|---|---|---|---|---|---|---|---|
linux-4.19 | possible deadlock in walk_component | syz | error | 126 | 743d | 1612d | 0/1 | upstream: reported syz repro on 2020/07/06 08:23 | |
upstream | possible deadlock in walk_component (3) kernfs | 1 | 244d | 240d | 0/28 | closed as dup on 2024/04/09 14:55 | |||
upstream | possible deadlock in walk_component fs | 11 | 1524d | 1738d | 0/28 | auto-closed as invalid on 2021/01/29 13:43 | |||
upstream | possible deadlock in walk_component (2) kernfs | 2 | 466d | 504d | 0/28 | auto-obsoleted due to no activity on 2023/12/03 10:44 |
====================================================== WARNING: possible circular locking dependency detected 6.12.0-rc4-syzkaller-00261-g850925a8133c #0 Not tainted ------------------------------------------------------ syz.9.3223/18559 is trying to acquire lock: ffff8880773712c0 (&ovl_i_mutex_dir_key[depth]){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:825 [inline] ffff8880773712c0 (&ovl_i_mutex_dir_key[depth]){++++}-{3:3}, at: lookup_slow fs/namei.c:1748 [inline] ffff8880773712c0 (&ovl_i_mutex_dir_key[depth]){++++}-{3:3}, at: walk_component+0x342/0x5b0 fs/namei.c:2053 but task is already holding lock: ffff88801286c088 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x27b/0x500 fs/kernfs/file.c:325 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #3 (&of->mutex){+.+.}-{3:3}: __mutex_lock_common kernel/locking/mutex.c:608 [inline] __mutex_lock+0x175/0x9c0 kernel/locking/mutex.c:752 kernfs_fop_write_iter+0x27b/0x500 fs/kernfs/file.c:325 iter_file_splice_write+0x90f/0x10b0 fs/splice.c:743 do_splice_from fs/splice.c:941 [inline] do_splice+0x145c/0x1f60 fs/splice.c:1354 __do_splice+0x327/0x360 fs/splice.c:1436 __do_sys_splice fs/splice.c:1652 [inline] __se_sys_splice fs/splice.c:1634 [inline] __x64_sys_splice+0x1cd/0x270 fs/splice.c:1634 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #2 (&pipe->mutex){+.+.}-{3:3}: __mutex_lock_common kernel/locking/mutex.c:608 [inline] __mutex_lock+0x175/0x9c0 kernel/locking/mutex.c:752 pipe_lock fs/pipe.c:92 [inline] pipe_lock+0x64/0x80 fs/pipe.c:89 iter_file_splice_write+0x1eb/0x10b0 fs/splice.c:687 do_splice_from fs/splice.c:941 [inline] do_splice+0x145c/0x1f60 fs/splice.c:1354 __do_splice+0x327/0x360 fs/splice.c:1436 __do_sys_splice fs/splice.c:1652 [inline] __se_sys_splice fs/splice.c:1634 [inline] __x64_sys_splice+0x1cd/0x270 fs/splice.c:1634 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #1 (sb_writers#6){.+.+}-{0:0}: percpu_down_read include/linux/percpu-rwsem.h:51 [inline] __sb_start_write include/linux/fs.h:1716 [inline] sb_start_write include/linux/fs.h:1852 [inline] mnt_want_write+0x6f/0x450 fs/namespace.c:515 ovl_create_object+0x12e/0x300 fs/overlayfs/dir.c:642 lookup_open.isra.0+0x1174/0x14c0 fs/namei.c:3595 open_last_lookups fs/namei.c:3694 [inline] path_openat+0x904/0x2d60 fs/namei.c:3930 do_filp_open+0x1dc/0x430 fs/namei.c:3960 do_sys_openat2+0x17a/0x1e0 fs/open.c:1415 do_sys_open fs/open.c:1430 [inline] __do_sys_creat fs/open.c:1508 [inline] __se_sys_creat fs/open.c:1502 [inline] __x64_sys_creat+0xcd/0x120 fs/open.c:1502 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #0 (&ovl_i_mutex_dir_key[depth]){++++}-{3:3}: check_prev_add kernel/locking/lockdep.c:3161 [inline] check_prevs_add kernel/locking/lockdep.c:3280 [inline] validate_chain kernel/locking/lockdep.c:3904 [inline] __lock_acquire+0x250b/0x3ce0 kernel/locking/lockdep.c:5202 lock_acquire.part.0+0x11b/0x380 kernel/locking/lockdep.c:5825 down_read+0x9a/0x330 kernel/locking/rwsem.c:1524 inode_lock_shared include/linux/fs.h:825 [inline] lookup_slow fs/namei.c:1748 [inline] walk_component+0x342/0x5b0 fs/namei.c:2053 lookup_last fs/namei.c:2556 [inline] path_lookupat+0x17f/0x770 fs/namei.c:2580 filename_lookup+0x1e5/0x5b0 fs/namei.c:2609 kern_path+0x35/0x50 fs/namei.c:2717 lookup_bdev+0xd9/0x280 block/bdev.c:1164 resume_store+0x1d8/0x460 kernel/power/hibernate.c:1239 kobj_attr_store+0x55/0x80 lib/kobject.c:840 sysfs_kf_write+0x117/0x170 fs/sysfs/file.c:136 kernfs_fop_write_iter+0x33d/0x500 fs/kernfs/file.c:334 new_sync_write fs/read_write.c:590 [inline] vfs_write+0x5ae/0x1150 fs/read_write.c:683 ksys_write+0x12f/0x260 fs/read_write.c:736 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 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.9.3223/18559: #0: ffff888032fb7438 (&f->f_pos_lock){+.+.}-{3:3}, at: fdget_pos+0x24c/0x360 fs/file.c:1160 #1: ffff88807c976420 (sb_writers#9){.+.+}-{0:0}, at: ksys_write+0x12f/0x260 fs/read_write.c:736 #2: ffff88801286c088 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x27b/0x500 fs/kernfs/file.c:325 #3: ffff888140ec54b8 (kn->active#83){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x29e/0x500 fs/kernfs/file.c:326 stack backtrace: CPU: 1 UID: 0 PID: 18559 Comm: syz.9.3223 Not tainted 6.12.0-rc4-syzkaller-00261-g850925a8133c #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Call Trace: <TASK> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120 print_circular_bug+0x41c/0x610 kernel/locking/lockdep.c:2074 check_noncircular+0x31a/0x400 kernel/locking/lockdep.c:2206 check_prev_add kernel/locking/lockdep.c:3161 [inline] check_prevs_add kernel/locking/lockdep.c:3280 [inline] validate_chain kernel/locking/lockdep.c:3904 [inline] __lock_acquire+0x250b/0x3ce0 kernel/locking/lockdep.c:5202 lock_acquire.part.0+0x11b/0x380 kernel/locking/lockdep.c:5825 down_read+0x9a/0x330 kernel/locking/rwsem.c:1524 inode_lock_shared include/linux/fs.h:825 [inline] lookup_slow fs/namei.c:1748 [inline] walk_component+0x342/0x5b0 fs/namei.c:2053 lookup_last fs/namei.c:2556 [inline] path_lookupat+0x17f/0x770 fs/namei.c:2580 filename_lookup+0x1e5/0x5b0 fs/namei.c:2609 kern_path+0x35/0x50 fs/namei.c:2717 lookup_bdev+0xd9/0x280 block/bdev.c:1164 resume_store+0x1d8/0x460 kernel/power/hibernate.c:1239 kobj_attr_store+0x55/0x80 lib/kobject.c:840 sysfs_kf_write+0x117/0x170 fs/sysfs/file.c:136 kernfs_fop_write_iter+0x33d/0x500 fs/kernfs/file.c:334 new_sync_write fs/read_write.c:590 [inline] vfs_write+0x5ae/0x1150 fs/read_write.c:683 ksys_write+0x12f/0x260 fs/read_write.c:736 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f767157e719 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:00007f767229e038 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 00007f7671735f80 RCX: 00007f767157e719 RDX: 0000000000000012 RSI: 0000000020000040 RDI: 0000000000000006 RBP: 00007f76715f132e R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007f7671735f80 R15: 00007ffed5c4ef78 </TASK> PM: Image not found (code -6)