====================================================== WARNING: possible circular locking dependency detected 4.19.124-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.1/807 is trying to acquire lock: 00000000670b38b8 (&ovl_i_mutex_dir_key[depth]){++++}, at: inode_lock_shared include/linux/fs.h:758 [inline] 00000000670b38b8 (&ovl_i_mutex_dir_key[depth]){++++}, at: lookup_slow+0x43/0x70 fs/namei.c:1688 but task is already holding lock: 00000000db72e403 (&sig->cred_guard_mutex){+.+.}, at: __do_sys_perf_event_open kernel/events/core.c:10611 [inline] 00000000db72e403 (&sig->cred_guard_mutex){+.+.}, at: __se_sys_perf_event_open+0x1941/0x2830 kernel/events/core.c:10520 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #3 (&sig->cred_guard_mutex){+.+.}: lock_trace+0x45/0xe0 fs/proc/base.c:402 proc_pid_syscall+0x94/0x240 fs/proc/base.c:635 proc_single_show+0xeb/0x170 fs/proc/base.c:755 seq_read+0x4b9/0x10c0 fs/seq_file.c:229 do_loop_readv_writev fs/read_write.c:701 [inline] do_loop_readv_writev fs/read_write.c:688 [inline] do_iter_read+0x46b/0x640 fs/read_write.c:925 vfs_readv+0xf0/0x160 fs/read_write.c:987 do_preadv+0x1b6/0x270 fs/read_write.c:1071 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe -> #2 (&p->lock){+.+.}: seq_read+0x6b/0x10c0 fs/seq_file.c:161 do_loop_readv_writev fs/read_write.c:701 [inline] do_loop_readv_writev fs/read_write.c:688 [inline] do_iter_read+0x46b/0x640 fs/read_write.c:925 vfs_readv+0xf0/0x160 fs/read_write.c:987 kernel_readv fs/splice.c:362 [inline] default_file_splice_read+0x477/0x970 fs/splice.c:417 do_splice_to+0x10e/0x160 fs/splice.c:881 splice_direct_to_actor+0x2b9/0x8d0 fs/splice.c:959 do_splice_direct+0x1a8/0x270 fs/splice.c:1068 do_sendfile+0x549/0xc10 fs/read_write.c:1447 __do_sys_sendfile64 fs/read_write.c:1508 [inline] __se_sys_sendfile64+0x147/0x160 fs/read_write.c:1494 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe -> #1 (sb_writers#3){.+.+}: sb_start_write include/linux/fs.h:1579 [inline] mnt_want_write+0x3a/0xb0 fs/namespace.c:360 ovl_create_object+0x96/0x290 fs/overlayfs/dir.c:600 lookup_open+0x869/0x1980 fs/namei.c:3235 do_last fs/namei.c:3327 [inline] path_openat+0x10ee/0x2eb0 fs/namei.c:3537 do_filp_open+0x1a1/0x280 fs/namei.c:3567 do_sys_open+0x3aa/0x510 fs/open.c:1085 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe -> #0 (&ovl_i_mutex_dir_key[depth]){++++}: down_read+0x37/0xb0 kernel/locking/rwsem.c:24 inode_lock_shared include/linux/fs.h:758 [inline] lookup_slow+0x43/0x70 fs/namei.c:1688 walk_component+0x759/0xd30 fs/namei.c:1811 lookup_last fs/namei.c:2274 [inline] path_lookupat.isra.0+0x1f5/0x8c0 fs/namei.c:2319 filename_lookup+0x1b0/0x410 fs/namei.c:2349 create_local_trace_uprobe+0x82/0x480 kernel/trace/trace_uprobe.c:1356 perf_uprobe_init+0x128/0x200 kernel/trace/trace_event_perf.c:317 perf_uprobe_event_init+0xf8/0x190 kernel/events/core.c:8582 perf_try_init_event+0x124/0x2e0 kernel/events/core.c:9855 perf_init_event kernel/events/core.c:9886 [inline] perf_event_alloc.part.0+0x17e9/0x2f30 kernel/events/core.c:10160 perf_event_alloc kernel/events/core.c:10530 [inline] __do_sys_perf_event_open kernel/events/core.c:10631 [inline] __se_sys_perf_event_open+0x553/0x2830 kernel/events/core.c:10520 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe other info that might help us debug this: Chain exists of: &ovl_i_mutex_dir_key[depth] --> &p->lock --> &sig->cred_guard_mutex Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&sig->cred_guard_mutex); lock(&p->lock); lock(&sig->cred_guard_mutex); lock(&ovl_i_mutex_dir_key[depth]); *** DEADLOCK *** 2 locks held by syz-executor.1/807: #0: 00000000db72e403 (&sig->cred_guard_mutex){+.+.}, at: __do_sys_perf_event_open kernel/events/core.c:10611 [inline] #0: 00000000db72e403 (&sig->cred_guard_mutex){+.+.}, at: __se_sys_perf_event_open+0x1941/0x2830 kernel/events/core.c:10520 #1: 00000000aa01b13e (&pmus_srcu){....}, at: perf_event_alloc.part.0+0xe14/0x2f30 kernel/events/core.c:10156 stack backtrace: CPU: 0 PID: 807 Comm: syz-executor.1 Not tainted 4.19.124-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x1fc/0x2fe lib/dump_stack.c:118 print_circular_bug.isra.0.cold+0x2dc/0x425 kernel/locking/lockdep.c:1221 check_prev_add kernel/locking/lockdep.c:1865 [inline] check_prevs_add kernel/locking/lockdep.c:1978 [inline] validate_chain kernel/locking/lockdep.c:2419 [inline] __lock_acquire+0x3145/0x4380 kernel/locking/lockdep.c:3415 lock_acquire+0x170/0x3c0 kernel/locking/lockdep.c:3907 down_read+0x37/0xb0 kernel/locking/rwsem.c:24 inode_lock_shared include/linux/fs.h:758 [inline] lookup_slow+0x43/0x70 fs/namei.c:1688 walk_component+0x759/0xd30 fs/namei.c:1811 lookup_last fs/namei.c:2274 [inline] path_lookupat.isra.0+0x1f5/0x8c0 fs/namei.c:2319 filename_lookup+0x1b0/0x410 fs/namei.c:2349 create_local_trace_uprobe+0x82/0x480 kernel/trace/trace_uprobe.c:1356 perf_uprobe_init+0x128/0x200 kernel/trace/trace_event_perf.c:317 perf_uprobe_event_init+0xf8/0x190 kernel/events/core.c:8582 perf_try_init_event+0x124/0x2e0 kernel/events/core.c:9855 perf_init_event kernel/events/core.c:9886 [inline] perf_event_alloc.part.0+0x17e9/0x2f30 kernel/events/core.c:10160 perf_event_alloc kernel/events/core.c:10530 [inline] __do_sys_perf_event_open kernel/events/core.c:10631 [inline] __se_sys_perf_event_open+0x553/0x2830 kernel/events/core.c:10520 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x45ca29 Code: 0d b7 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 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 0f 83 db b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00 RSP: 002b:00007faeed0a2c78 EFLAGS: 00000246 ORIG_RAX: 000000000000012a RAX: ffffffffffffffda RBX: 00000000004f95c0 RCX: 000000000045ca29 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00000000200000c0 RBP: 000000000078bf00 R08: 0000000000000000 R09: 0000000000000000 R10: ffffffffffffffff R11: 0000000000000246 R12: 00000000ffffffff R13: 000000000000081e R14: 00000000004caf71 R15: 00007faeed0a36d4 netlink: 'syz-executor.5': attribute type 25 has an invalid length. overlayfs: failed to resolve './file0': -2