====================================================== WARNING: possible circular locking dependency detected 4.19.108-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.5/18623 is trying to acquire lock: 000000002004bc29 (&ovl_i_mutex_dir_key[depth]){++++}, at: inode_lock_shared include/linux/fs.h:757 [inline] 000000002004bc29 (&ovl_i_mutex_dir_key[depth]){++++}, at: lookup_slow+0x43/0x70 fs/namei.c:1688 but task is already holding lock: 00000000be32e6c0 (&sig->cred_guard_mutex){+.+.}, at: __do_sys_perf_event_open+0x7b5/0x2830 kernel/events/core.c:10601 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_stack+0x12c/0x290 fs/proc/base.c:452 proc_single_show+0xeb/0x170 fs/proc/base.c:755 seq_read+0x4b9/0x10f0 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 kernel_readv fs/splice.c:362 [inline] default_file_splice_read+0x478/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 fs/read_write.c:1494 [inline] __x64_sys_sendfile64+0x1cc/0x210 fs/read_write.c:1494 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe -> #2 (&p->lock){+.+.}: seq_read+0x6b/0x10f0 fs/seq_file.c:161 proc_reg_read+0x1bd/0x280 fs/proc/inode.c:231 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+0x478/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 fs/read_write.c:1494 [inline] __x64_sys_sendfile64+0x1cc/0x210 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#4){.+.+}: sb_start_write include/linux/fs.h:1578 [inline] mnt_want_write+0x3a/0xb0 fs/namespace.c:360 ovl_create_object+0x96/0x290 fs/overlayfs/dir.c:600 lookup_open+0x11f6/0x19b0 fs/namei.c:3235 do_last fs/namei.c:3327 [inline] path_openat+0x13cb/0x4200 fs/namei.c:3537 do_filp_open+0x1a1/0x280 fs/namei.c:3567 do_sys_open+0x3c0/0x500 fs/open.c:1088 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:757 [inline] lookup_slow+0x43/0x70 fs/namei.c:1688 walk_component+0x70a/0x1ee0 fs/namei.c:1811 lookup_last fs/namei.c:2274 [inline] path_lookupat.isra.0+0x1f5/0x8d0 fs/namei.c:2319 filename_lookup+0x1b0/0x410 fs/namei.c:2349 create_local_trace_uprobe+0x82/0x490 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:8572 perf_try_init_event+0x124/0x2e0 kernel/events/core.c:9845 perf_init_event kernel/events/core.c:9876 [inline] perf_event_alloc.part.0+0x1e5f/0x2f90 kernel/events/core.c:10150 perf_event_alloc kernel/events/core.c:10520 [inline] __do_sys_perf_event_open+0x902/0x2830 kernel/events/core.c:10621 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.5/18623: #0: 00000000be32e6c0 (&sig->cred_guard_mutex){+.+.}, at: __do_sys_perf_event_open+0x7b5/0x2830 kernel/events/core.c:10601 #1: 0000000031bf218b (&pmus_srcu){....}, at: perf_event_alloc.part.0+0xda7/0x2f90 kernel/events/core.c:10146 stack backtrace: CPU: 0 PID: 18623 Comm: syz-executor.5 Not tainted 4.19.108-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+0x188/0x20d lib/dump_stack.c:118 print_circular_bug.isra.0.cold+0x1c4/0x282 kernel/locking/lockdep.c:1221 check_prev_add kernel/locking/lockdep.c:1861 [inline] check_prevs_add kernel/locking/lockdep.c:1974 [inline] validate_chain kernel/locking/lockdep.c:2415 [inline] __lock_acquire+0x2e19/0x49c0 kernel/locking/lockdep.c:3411 lock_acquire+0x170/0x400 kernel/locking/lockdep.c:3903 down_read+0x37/0xb0 kernel/locking/rwsem.c:24 inode_lock_shared include/linux/fs.h:757 [inline] lookup_slow+0x43/0x70 fs/namei.c:1688 walk_component+0x70a/0x1ee0 fs/namei.c:1811 lookup_last fs/namei.c:2274 [inline] path_lookupat.isra.0+0x1f5/0x8d0 fs/namei.c:2319 filename_lookup+0x1b0/0x410 fs/namei.c:2349 create_local_trace_uprobe+0x82/0x490 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:8572 perf_try_init_event+0x124/0x2e0 kernel/events/core.c:9845 perf_init_event kernel/events/core.c:9876 [inline] perf_event_alloc.part.0+0x1e5f/0x2f90 kernel/events/core.c:10150 perf_event_alloc kernel/events/core.c:10520 [inline] __do_sys_perf_event_open+0x902/0x2830 kernel/events/core.c:10621 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x45c4a9 Code: ad b6 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 7b b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00 RSP: 002b:00007f0b4a2bcc78 EFLAGS: 00000246 ORIG_RAX: 000000000000012a RAX: ffffffffffffffda RBX: 00007f0b4a2bd6d4 RCX: 000000000045c4a9 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000020000080 RBP: 000000000076bf20 R08: 0000000000000000 R09: 0000000000000000 R10: ffffffffffffffff R11: 0000000000000246 R12: 00000000ffffffff R13: 0000000000000813 R14: 00000000004ca90b R15: 000000000076bf2c REISERFS warning (device loop4): sh-2021 reiserfs_fill_super: can not find reiserfs on loop4 REISERFS warning (device loop4): sh-2021 reiserfs_fill_super: can not find reiserfs on loop4 REISERFS warning (device loop4): sh-2021 reiserfs_fill_super: can not find reiserfs on loop4 Started in network mode Own node identity , cluster identity 4711 Failed to set node id, please configure manually Enabling of bearer rejected, failed to enable media REISERFS warning (device loop4): super-6502 reiserfs_getopt: unknown mount option "" REISERFS warning (device loop4): super-6502 reiserfs_getopt: unknown mount option "" REISERFS warning (device loop4): super-6502 reiserfs_getopt: unknown mount option "" overlayfs: failed to resolve './file0': -2 overlayfs: failed to resolve './file0': -2 overlayfs: failed to resolve './file0': -2 overlayfs: failed to resolve './file1': -2 hid-generic 0000:0000:0000.0008: ignoring exceeding usage max hid-generic 0000:0000:0000.0008: hidraw0: HID v0.00 Device [syz1] on sz1 overlayfs: failed to resolve './file1': -2 hid-generic 0000:0000:0000.0009: ignoring exceeding usage max hid-generic 0000:0000:0000.0009: hidraw0: HID v0.00 Device [syz1] on sz1 hid-generic 0000:0000:0000.000A: ignoring exceeding usage max overlayfs: failed to resolve './file1': -2 hid-generic 0000:0000:0000.000A: hidraw0: HID v0.00 Device [syz1] on sz1 hid-generic 0000:0000:0000.000B: ignoring exceeding usage max hid-generic 0000:0000:0000.000B: hidraw0: HID v0.00 Device [syz1] on sz1 overlayfs: failed to resolve './file1': -2 hid-generic 0000:0000:0000.000C: ignoring exceeding usage max hid-generic 0000:0000:0000.000C: hidraw0: HID v0.00 Device [syz1] on sz1 overlayfs: failed to resolve './file1': -2 hid-generic 0000:0000:0000.000D: ignoring exceeding usage max hid-generic 0000:0000:0000.000D: hidraw0: HID v0.00 Device [syz1] on sz1 xt_connbytes: Forcing CT accounting to be enabled overlayfs: failed to resolve './file1': -2 xt_CT: You must specify a L4 protocol and not use inversions on it xt_CT: You must specify a L4 protocol and not use inversions on it xt_CT: You must specify a L4 protocol and not use inversions on it xt_CT: You must specify a L4 protocol and not use inversions on it xt_CT: You must specify a L4 protocol and not use inversions on it xt_CT: You must specify a L4 protocol and not use inversions on it overlayfs: failed to resolve './file0': -2 xt_CT: You must specify a L4 protocol and not use inversions on it overlayfs: failed to resolve './file0': -2 xt_CT: You must specify a L4 protocol and not use inversions on it overlayfs: failed to resolve './file0': -2 xt_CT: You must specify a L4 protocol and not use inversions on it overlayfs: missing 'lowerdir' overlayfs: missing 'lowerdir' overlayfs: missing 'lowerdir' overlayfs: missing 'lowerdir' overlayfs: missing 'lowerdir' overlayfs: missing 'lowerdir' Scheduler tracepoints stat_sleep, stat_iowait, stat_blocked and stat_runtime require the kernel parameter schedstats=enable or kernel.sched_schedstats=1 overlayfs: missing 'lowerdir' overlayfs: missing 'lowerdir' overlayfs: missing 'lowerdir' overlayfs: option "workdir=." is useless in a non-upper mount, ignore overlayfs: at least 2 lowerdir are needed while upperdir nonexistent