======================================================
WARNING: possible circular locking dependency detected
6.3.0-rc2-next-20230315 #1 Not tainted
------------------------------------------------------
syz-executor.7/12674 is trying to acquire lock:
ffffffff85684d90 (dup_mmap_sem){++++}-{0:0}, at: register_for_each_vma+0x2c/0xd50

but task is already holding lock:
ffff888037faf090 (&uprobe->register_rwsem){+.+.}-{3:3}, at: __uprobe_register+0x5cc/0x940

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #3 (&uprobe->register_rwsem){+.+.}-{3:3}:
       down_write+0x92/0x1f0
       __uprobe_register+0x5cc/0x940
       probe_event_enable+0x447/0xb40
       trace_uprobe_register+0x5c/0x990
       perf_trace_event_init+0x516/0xa20
       perf_uprobe_init+0x177/0x220
       perf_uprobe_event_init+0x103/0x1d0
       perf_try_init_event+0x130/0x570
       perf_event_alloc.part.0+0xf22/0x39b0
       __do_sys_perf_event_open+0x4d3/0x2a60
       do_syscall_64+0x3f/0x90
       entry_SYSCALL_64_after_hwframe+0x72/0xdc

-> #2 (event_mutex){+.+.}-{3:3}:
       __mutex_lock+0x133/0x14a0
       perf_trace_destroy+0x27/0x1c0
       _free_event+0x207/0x1150
       perf_mmap_close+0x54b/0xef0
       remove_vma+0x88/0x170
       do_vmi_align_munmap.constprop.0+0xc64/0x1190
       do_vmi_munmap+0x1ec/0x2c0
       mmap_region+0x1f1/0x24a0
       do_mmap+0x82c/0xf50
       vm_mmap_pgoff+0x1a6/0x3a0
       ksys_mmap_pgoff+0x3a3/0x4f0
       do_syscall_64+0x3f/0x90
       entry_SYSCALL_64_after_hwframe+0x72/0xdc

-> #1 (&mm->mmap_lock){++++}-{3:3}:
       down_write_killable+0x97/0x230
       dup_mmap+0x10b/0x1780
       copy_process+0x6ffc/0x74e0
       kernel_clone+0xeb/0x8c0
       __do_sys_clone+0xba/0x100
       do_syscall_64+0x3f/0x90
       entry_SYSCALL_64_after_hwframe+0x72/0xdc

-> #0 (dup_mmap_sem){++++}-{0:0}:
       __lock_acquire+0x2da7/0x63b0
       lock_acquire.part.0+0xec/0x320
       percpu_down_write+0x51/0x330
       register_for_each_vma+0x2c/0xd50
       __uprobe_register+0x661/0x940
       probe_event_enable+0x447/0xb40
       trace_uprobe_register+0x5c/0x990
       perf_trace_event_init+0x516/0xa20
       perf_uprobe_init+0x177/0x220
       perf_uprobe_event_init+0x103/0x1d0
       perf_try_init_event+0x130/0x570
       perf_event_alloc.part.0+0xf22/0x39b0
       __do_sys_perf_event_open+0x4d3/0x2a60
       do_syscall_64+0x3f/0x90
       entry_SYSCALL_64_after_hwframe+0x72/0xdc

other info that might help us debug this:

Chain exists of:
  dup_mmap_sem --> event_mutex --> &uprobe->register_rwsem

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&uprobe->register_rwsem);
                               lock(event_mutex);
                               lock(&uprobe->register_rwsem);
  lock(dup_mmap_sem);

 *** DEADLOCK ***

3 locks held by syz-executor.7/12674:
 #0: ffffffff87b21430 (&pmus_srcu){.+.+}-{0:0}, at: perf_event_alloc.part.0+0xcd2/0x39b0
 #1: ffffffff85663e68 (event_mutex){+.+.}-{3:3}, at: perf_uprobe_init+0x16c/0x220
 #2: ffff888037faf090 (&uprobe->register_rwsem){+.+.}-{3:3}, at: __uprobe_register+0x5cc/0x940

stack backtrace:
CPU: 1 PID: 12674 Comm: syz-executor.7 Not tainted 6.3.0-rc2-next-20230315 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014
Call Trace:
 <TASK>
 dump_stack_lvl+0x91/0xf0
 check_noncircular+0x263/0x2e0
 __lock_acquire+0x2da7/0x63b0
 lock_acquire.part.0+0xec/0x320
 percpu_down_write+0x51/0x330
 register_for_each_vma+0x2c/0xd50
 __uprobe_register+0x661/0x940
 probe_event_enable+0x447/0xb40
 trace_uprobe_register+0x5c/0x990
 perf_trace_event_init+0x516/0xa20
 perf_uprobe_init+0x177/0x220
 perf_uprobe_event_init+0x103/0x1d0
 perf_try_init_event+0x130/0x570
 perf_event_alloc.part.0+0xf22/0x39b0
 __do_sys_perf_event_open+0x4d3/0x2a60
 do_syscall_64+0x3f/0x90
 entry_SYSCALL_64_after_hwframe+0x72/0xdc
RIP: 0033:0x7fdf92dbab19
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 bc ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fdf90330188 EFLAGS: 00000246 ORIG_RAX: 000000000000012a
RAX: ffffffffffffffda RBX: 00007fdf92ecdf60 RCX: 00007fdf92dbab19
RDX: 0000000000000000 RSI: ffffffffffffffff RDI: 0000000020000280
RBP: 00007fdf92e14f6d R08: 0000000000000000 R09: 0000000000000000
R10: ffffffffffffffff R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffde408102f R14: 00007fdf90330300 R15: 0000000000022000
 </TASK>
SELinux: unrecognized netlink message: protocol=6 nlmsg_type=263 sclass=netlink_xfrm_socket pid=12697 comm=syz-executor.5
SELinux: unrecognized netlink message: protocol=6 nlmsg_type=263 sclass=netlink_xfrm_socket pid=12714 comm=syz-executor.5
SELinux: unrecognized netlink message: protocol=6 nlmsg_type=263 sclass=netlink_xfrm_socket pid=12731 comm=syz-executor.5
netlink: 4 bytes leftover after parsing attributes in process `syz-executor.3'.
netlink: 4 bytes leftover after parsing attributes in process `syz-executor.3'.
netlink: 4 bytes leftover after parsing attributes in process `syz-executor.3'.
netlink: 4 bytes leftover after parsing attributes in process `syz-executor.3'.