====================================================== WARNING: possible circular locking dependency detected 4.14.305-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.0/9942 is trying to acquire lock: (&event->child_mutex){+.+.}, at: [] perf_event_for_each_child+0x82/0x140 kernel/events/core.c:4690 but task is already holding lock: (&cpuctx_mutex){+.+.}, at: [] 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:11293 perf_event_init+0x2cc/0x308 kernel/events/core.c:11340 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:11287 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/0x165 init/main.c:1006 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:406 -> #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 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:8145 perf_try_init_event+0x15b/0x1f0 kernel/events/core.c:9381 perf_init_event kernel/events/core.c:9419 [inline] perf_event_alloc.part.0+0xe2d/0x2640 kernel/events/core.c:9679 perf_event_alloc kernel/events/core.c:10049 [inline] SYSC_perf_event_open kernel/events/core.c:10153 [inline] SyS_perf_event_open+0x683/0x2530 kernel/events/core.c:10039 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x5e/0xd3 -> #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:8145 perf_try_init_event+0x15b/0x1f0 kernel/events/core.c:9381 perf_init_event kernel/events/core.c:9419 [inline] perf_event_alloc.part.0+0xe2d/0x2640 kernel/events/core.c:9679 perf_event_alloc kernel/events/core.c:10049 [inline] SYSC_perf_event_open kernel/events/core.c:10153 [inline] SyS_perf_event_open+0x683/0x2530 kernel/events/core.c:10039 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x5e/0xd3 -> #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:915 SYSC_exit kernel/exit.c:1006 [inline] SyS_exit+0x1e/0x20 kernel/exit.c:1004 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x5e/0xd3 -> #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+0x5e/0xd3 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.0/9942: #0: (&cpuctx_mutex){+.+.}, at: [] perf_event_ctx_lock_nested+0x14d/0x2c0 kernel/events/core.c:1241 stack backtrace: CPU: 0 PID: 9942 Comm: syz-executor.0 Not tainted 4.14.305-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/21/2023 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+0x5e/0xd3 RIP: 0033:0x7f083b5540f9 RSP: 002b:00007f0839ac6168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f083b673f80 RCX: 00007f083b5540f9 RDX: 0000000000000000 RSI: 0000000000002401 RDI: 0000000000000003 RBP: 00007f083b5afae9 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffd489bc60f R14: 00007f0839ac6300 R15: 0000000000022000 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. audit: type=1800 audit(1676063815.209:2): pid=10373 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.1" name="file0" dev="sda1" ino=13996 res=0 can: request_module (can-proto-0) failed. unregister_netdevice: waiting for ip6gre0 to become free. Usage count = -1 audit: type=1800 audit(1676063817.289:3): pid=10702 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.2" name=".pending_reads" dev="sda1" ino=14037 res=0 audit: type=1326 audit(1676063817.679:4): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=10735 comm="syz-executor.3" exe="/root/syz-executor.3" sig=0 arch=c000003e syscall=202 compat=0 ip=0x7f94622240f9 code=0x7ffc0000 netlink: 1024 bytes leftover after parsing attributes in process `syz-executor.2'. audit: type=1326 audit(1676063817.679:5): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=10735 comm="syz-executor.3" exe="/root/syz-executor.3" sig=0 arch=c000003e syscall=202 compat=0 ip=0x7f94622240f9 code=0x7ffc0000 netlink: 1024 bytes leftover after parsing attributes in process `syz-executor.2'. TCP: request_sock_TCPv6: Possible SYN flooding on port 20002. Sending cookies. Check SNMP counters. caif:caif_disconnect_client(): nothing to disconnect audit: type=1804 audit(1676063817.799:6): pid=10783 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.0" name="/root/syzkaller-testdir2079927020/syzkaller.ebD8p9/78/bus" dev="sda1" ino=14020 res=1 netlink: 1024 bytes leftover after parsing attributes in process `syz-executor.2'. netlink: 1024 bytes leftover after parsing attributes in process `syz-executor.2'. audit: type=1804 audit(1676063818.689:7): pid=10872 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.0" name="/root/syzkaller-testdir2079927020/syzkaller.ebD8p9/79/bus" dev="sda1" ino=13991 res=1 mmap: syz-executor.5 (10887) uses deprecated remap_file_pages() syscall. See Documentation/vm/remap_file_pages.txt. FAT-fs (loop2): mounting with "discard" option, but the device does not support discard audit: type=1804 audit(1676063818.999:8): pid=10927 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.0" name="/root/syzkaller-testdir2079927020/syzkaller.ebD8p9/80/bus" dev="sda1" ino=13988 res=1 audit: type=1804 audit(1676063819.029:9): pid=10926 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="ToMToU" comm="syz-executor.0" name="/root/syzkaller-testdir2079927020/syzkaller.ebD8p9/80/bus" dev="sda1" ino=13988 res=1 BTRFS: device fsid d552757d-9c39-40e3-95f0-16d819589928 devid 1 transid 8 /dev/loop1 audit: type=1804 audit(1676063819.029:10): pid=10927 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.0" name="/root/syzkaller-testdir2079927020/syzkaller.ebD8p9/80/bus" dev="sda1" ino=13988 res=1 BTRFS error (device loop1): unsupported checksum algorithm 2 audit: type=1804 audit(1676063819.029:11): pid=10926 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="ToMToU" comm="syz-executor.0" name="/root/syzkaller-testdir2079927020/syzkaller.ebD8p9/80/bus" dev="sda1" ino=13988 res=1 BTRFS error (device loop1): superblock checksum mismatch BTRFS error (device loop1): open_ctree failed caif:caif_disconnect_client(): nothing to disconnect F2FS-fs (loop5): Found nat_bits in checkpoint process 'syz-executor.3' launched './file0' with NULL argv: empty string added F2FS-fs (loop5): Mounted with checkpoint version = 48b305e5 attempt to access beyond end of device loop5: rw=2049, want=45104, limit=40427 F2FS-fs (loop5): Found nat_bits in checkpoint F2FS-fs (loop5): Mounted with checkpoint version = 48b305e5 attempt to access beyond end of device loop5: rw=2049, want=45104, limit=40427