======================================================
WARNING: possible circular locking dependency detected
4.14.295-syzkaller #0 Not tainted
------------------------------------------------------
syz-executor.2/11194 is trying to acquire lock:
(&event->child_mutex){+.+.}, at: [<ffffffff81630f02>] perf_event_for_each_child+0x82/0x140 kernel/events/core.c:4690
but task is already holding lock:
(&cpuctx_mutex){+.+.}, at: [<ffffffff8163596d>] perf_event_ctx_lock_nested+0x14d/0x2c0 kernel/events/core.c:1241
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #5 (&cpuctx_mutex){+.+.}:
__mutex_lock_common kernel/locking/mutex.c:756 [inline]
__mutex_lock+0xc4/0x1310 kernel/locking/mutex.c:893
perf_event_init_cpu+0xb7/0x170 kernel/events/core.c:11286
perf_event_init+0x2cc/0x308 kernel/events/core.c:11333
start_kernel+0x45d/0x763 init/main.c:624
secondary_startup_64+0xa5/0xb0 arch/x86/kernel/head_64.S:240
-> #4 (pmus_lock){+.+.}:
__mutex_lock_common kernel/locking/mutex.c:756 [inline]
__mutex_lock+0xc4/0x1310 kernel/locking/mutex.c:893
perf_event_init_cpu+0x2c/0x170 kernel/events/core.c:11280
cpuhp_invoke_callback+0x1e6/0x1a80 kernel/cpu.c:186
cpuhp_up_callbacks kernel/cpu.c:574 [inline]
_cpu_up+0x21e/0x520 kernel/cpu.c:1193
do_cpu_up+0x9a/0x160 kernel/cpu.c:1229
smp_init+0x197/0x1ac kernel/smp.c:578
kernel_init_freeable+0x406/0x626 init/main.c:1074
kernel_init+0xd/0x161 init/main.c:1006
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404
-> #3 (cpu_hotplug_lock.rw_sem){++++}:
percpu_down_read_preempt_disable include/linux/percpu-rwsem.h:36 [inline]
percpu_down_read include/linux/percpu-rwsem.h:59 [inline]
cpus_read_lock+0x39/0xc0 kernel/cpu.c:297
static_key_slow_inc+0xe/0x20 kernel/jump_label.c:123
tracepoint_add_func+0x747/0xa40 kernel/tracepoint.c:269
tracepoint_probe_register_prio kernel/tracepoint.c:331 [inline]
tracepoint_probe_register+0x8c/0xc0 kernel/tracepoint.c:352
register_trace_kfree_skb include/trace/events/skb.h:15 [inline]
set_all_monitor_traces net/core/drop_monitor.c:264 [inline]
net_dm_cmd_trace net/core/drop_monitor.c:315 [inline]
net_dm_cmd_trace+0x275/0x3a0 net/core/drop_monitor.c:310
genl_family_rcv_msg+0x572/0xb20 net/netlink/genetlink.c:600
genl_rcv_msg+0xaf/0x140 net/netlink/genetlink.c:625
netlink_rcv_skb+0x125/0x390 net/netlink/af_netlink.c:2454
genl_rcv+0x24/0x40 net/netlink/genetlink.c:636
netlink_unicast_kernel net/netlink/af_netlink.c:1296 [inline]
netlink_unicast+0x437/0x610 net/netlink/af_netlink.c:1322
netlink_sendmsg+0x648/0xbc0 net/netlink/af_netlink.c:1893
sock_sendmsg_nosec net/socket.c:646 [inline]
sock_sendmsg+0xb5/0x100 net/socket.c:656
___sys_sendmsg+0x6c8/0x800 net/socket.c:2062
__sys_sendmsg+0xa3/0x120 net/socket.c:2096
SYSC_sendmsg net/socket.c:2107 [inline]
SyS_sendmsg+0x27/0x40 net/socket.c:2103
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
-> #2 (tracepoints_mutex){+.+.}:
__mutex_lock_common kernel/locking/mutex.c:756 [inline]
__mutex_lock+0xc4/0x1310 kernel/locking/mutex.c:893
tracepoint_probe_register_prio kernel/tracepoint.c:327 [inline]
tracepoint_probe_register+0x68/0xc0 kernel/tracepoint.c:352
trace_event_reg+0x272/0x330 kernel/trace/trace_events.c:305
perf_trace_event_reg kernel/trace/trace_event_perf.c:122 [inline]
perf_trace_event_init kernel/trace/trace_event_perf.c:197 [inline]
perf_trace_init+0x424/0xa30 kernel/trace/trace_event_perf.c:221
perf_tp_event_init+0x79/0xf0 kernel/events/core.c:8140
perf_try_init_event+0x15b/0x1f0 kernel/events/core.c:9374
perf_init_event kernel/events/core.c:9412 [inline]
perf_event_alloc.part.0+0xe2d/0x2640 kernel/events/core.c:9672
perf_event_alloc kernel/events/core.c:10042 [inline]
SYSC_perf_event_open kernel/events/core.c:10146 [inline]
SyS_perf_event_open+0x683/0x2530 kernel/events/core.c:10032
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
-> #1 (event_mutex){+.+.}:
__mutex_lock_common kernel/locking/mutex.c:756 [inline]
__mutex_lock+0xc4/0x1310 kernel/locking/mutex.c:893
perf_trace_destroy+0x23/0xf0 kernel/trace/trace_event_perf.c:234
_free_event+0x321/0xe20 kernel/events/core.c:4246
free_event+0x32/0x40 kernel/events/core.c:4273
perf_event_release_kernel+0x368/0x8a0 kernel/events/core.c:4417
perf_release+0x33/0x40 kernel/events/core.c:4443
__fput+0x25f/0x7a0 fs/file_table.c:210
task_work_run+0x11f/0x190 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0xa44/0x2850 kernel/exit.c:868
SYSC_exit kernel/exit.c:934 [inline]
SyS_exit+0x1e/0x20 kernel/exit.c:932
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
-> #0 (&event->child_mutex){+.+.}:
lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998
__mutex_lock_common kernel/locking/mutex.c:756 [inline]
__mutex_lock+0xc4/0x1310 kernel/locking/mutex.c:893
perf_event_for_each_child+0x82/0x140 kernel/events/core.c:4690
_perf_ioctl+0x471/0x1a60 kernel/events/core.c:4877
perf_ioctl+0x55/0x80 kernel/events/core.c:4889
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:500 [inline]
do_vfs_ioctl+0x75a/0xff0 fs/ioctl.c:684
SYSC_ioctl fs/ioctl.c:701 [inline]
SyS_ioctl+0x7f/0xb0 fs/ioctl.c:692
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
other info that might help us debug this:
Chain exists of:
&event->child_mutex --> pmus_lock --> &cpuctx_mutex
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(&cpuctx_mutex);
lock(pmus_lock);
lock(&cpuctx_mutex);
lock(&event->child_mutex);
*** DEADLOCK ***
1 lock held by syz-executor.2/11194:
#0: (&cpuctx_mutex){+.+.}, at: [<ffffffff8163596d>] perf_event_ctx_lock_nested+0x14d/0x2c0 kernel/events/core.c:1241
stack backtrace:
CPU: 0 PID: 11194 Comm: syz-executor.2 Not tainted 4.14.295-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x281 lib/dump_stack.c:58
print_circular_bug.constprop.0.cold+0x2d7/0x41e kernel/locking/lockdep.c:1258
check_prev_add kernel/locking/lockdep.c:1905 [inline]
check_prevs_add kernel/locking/lockdep.c:2022 [inline]
validate_chain kernel/locking/lockdep.c:2464 [inline]
__lock_acquire+0x2e0e/0x3f20 kernel/locking/lockdep.c:3491
lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998
__mutex_lock_common kernel/locking/mutex.c:756 [inline]
__mutex_lock+0xc4/0x1310 kernel/locking/mutex.c:893
perf_event_for_each_child+0x82/0x140 kernel/events/core.c:4690
_perf_ioctl+0x471/0x1a60 kernel/events/core.c:4877
perf_ioctl+0x55/0x80 kernel/events/core.c:4889
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:500 [inline]
do_vfs_ioctl+0x75a/0xff0 fs/ioctl.c:684
SYSC_ioctl fs/ioctl.c:701 [inline]
SyS_ioctl+0x7f/0xb0 fs/ioctl.c:692
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7f43868145a9
RSP: 002b:00007f4385187168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f4386934f80 RCX: 00007f43868145a9
RDX: 0000000000000000 RSI: 0000000000002401 RDI: 0000000000000003
RBP: 00007f438686f580 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffca1c743ff R14: 00007f4385187300 R15: 0000000000022000
EXT4-fs warning (device sda1): ext4_group_add:1669: No reserved GDT blocks, can't resize
EXT4-fs warning (device sda1): ext4_group_add:1669: No reserved GDT blocks, can't resize
EXT4-fs warning (device sda1): ext4_group_add:1669: No reserved GDT blocks, can't resize
EXT4-fs warning (device sda1): ext4_group_add:1669: No reserved GDT blocks, can't resize
process 'syz-executor.4' launched './file0' with NULL argv: empty string added
EXT4-fs warning (device sda1): ext4_group_add:1669: No reserved GDT blocks, can't resize
EXT4-fs warning (device sda1): ext4_group_add:1669: No reserved GDT blocks, can't resize
EXT4-fs warning (device sda1): ext4_group_add:1669: No reserved GDT blocks, can't resize
EXT4-fs warning (device sda1): ext4_group_add:1669: No reserved GDT blocks, can't resize
EXT4-fs warning (device sda1): ext4_group_add:1669: No reserved GDT blocks, can't resize
capability: warning: `syz-executor.2' uses deprecated v2 capabilities in a way that may be insecure
unregister_netdevice: waiting for ip6gre0 to become free. Usage count = -1
L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details.
PF_BRIDGE: RTM_SETLINK with unknown ifindex
sctp: [Deprecated]: syz-executor.1 (pid 11979) Use of int in max_burst socket option deprecated.
Use struct sctp_assoc_value instead
netlink: 8 bytes leftover after parsing attributes in process `syz-executor.2'.
netlink: 8 bytes leftover after parsing attributes in process `syz-executor.1'.
IPVS: set_ctl: invalid protocol: 0 172.20.20.170:0
netlink: 8 bytes leftover after parsing attributes in process `syz-executor.4'.
netlink: 8 bytes leftover after parsing attributes in process `syz-executor.0'.
netlink: 8 bytes leftover after parsing attributes in process `syz-executor.5'.
netlink: 160 bytes leftover after parsing attributes in process `syz-executor.4'.
IPVS: set_ctl: invalid protocol: 0 172.20.20.170:0