====================================================== WARNING: possible circular locking dependency detected 4.14.300-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.4/10340 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: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/0x167 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: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+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: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+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: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+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.4/10340: #0: (&cpuctx_mutex){+.+.}, at: [] perf_event_ctx_lock_nested+0x14d/0x2c0 kernel/events/core.c:1241 stack backtrace: CPU: 0 PID: 10340 Comm: syz-executor.4 Not tainted 4.14.300-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/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+0x5e/0xd3 syz-executor.5 uses obsolete (PF_INET,SOCK_PACKET) EXT4-fs (loop3): Ignoring removed orlov option 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. EXT4-fs (loop3): can't mount with dioread_nolock if block size != PAGE_SIZE Y4`Ҙ: renamed from lo Bearer rejected, not supported in standalone mode BTRFS: device fsid 24c7a497-3402-47dd-bef8-82358f5f30e0 devid 1 transid 8 /dev/loop3 BTRFS info (device loop3): enabling inode map caching BTRFS warning (device loop3): excessive commit interval 622039222 BTRFS info (device loop3): force zlib compression BTRFS info (device loop3): using free space tree BTRFS info (device loop3): has skinny extents BTRFS info (device loop3): enabling inode map caching BTRFS warning (device loop3): excessive commit interval 622039222 BTRFS info (device loop3): force zlib compression BTRFS info (device loop3): using free space tree BTRFS info (device loop3): has skinny extents unregister_netdevice: waiting for ip6gre0 to become free. Usage count = -1 BTRFS info (device loop3): enabling inode map caching BTRFS warning (device loop3): excessive commit interval 622039222 BTRFS info (device loop3): force zlib compression BTRFS info (device loop3): using free space tree BTRFS info (device loop3): has skinny extents ====================================================== WARNING: the mand mount option is being deprecated and will be removed in v5.15! ====================================================== BTRFS info (device loop3): enabling inode map caching BTRFS warning (device loop3): excessive commit interval 622039222 BTRFS info (device loop3): force zlib compression BTRFS info (device loop3): using free space tree BTRFS info (device loop3): has skinny extents EXT4-fs (sda1): re-mounted. Opts: (null) EXT4-fs (sda1): re-mounted. Opts: (null) tmpfs: No value for mount option 'none' UDF-fs: error (device loop5): udf_process_sequence: Block 96 of volume descriptor sequence is corrupted or we could not read it UDF-fs: INFO Mounting volume 'LinuxUDF', timestamp 2022/11/22 14:59 (1000) UDF-fs: error (device loop3): udf_process_sequence: Block 96 of volume descriptor sequence is corrupted or we could not read it UDF-fs: INFO Mounting volume 'LinuxUDF', timestamp 2022/11/22 14:59 (1000) UDF-fs: error (device loop5): udf_process_sequence: Block 96 of volume descriptor sequence is corrupted or we could not read it UDF-fs: INFO Mounting volume 'LinuxUDF', timestamp 2022/11/22 14:59 (1000) BTRFS: device fsid e417788f-7a09-42b2-9266-8ddc5d5d35d2 devid 1 transid 8 /dev/loop4 BTRFS error (device loop4): unsupported checksum algorithm 1 BTRFS error (device loop4): superblock checksum mismatch BTRFS error (device loop4): open_ctree failed kauditd_printk_skb: 5 callbacks suppressed audit: type=1804 audit(1669955688.034:17): pid=11109 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.4" name="/root/syzkaller-testdir320806883/syzkaller.NR6zX0/89/bus" dev="sda1" ino=14150 res=1 EXT4-fs (loop2): Mount option "nouser_xattr" will be removed by 3.5 Contact linux-ext4@vger.kernel.org if you think we should keep it. UDF-fs: error (device loop3): udf_process_sequence: Block 96 of volume descriptor sequence is corrupted or we could not read it UDF-fs: error (device loop5): udf_process_sequence: Block 96 of volume descriptor sequence is corrupted or we could not read it EXT4-fs (loop2): Ignoring removed nobh option UDF-fs: INFO Mounting volume 'LinuxUDF', timestamp 2022/11/22 14:59 (1000) EXT4-fs: Warning: mounting with data=journal disables delayed allocation and O_DIRECT support! UDF-fs: INFO Mounting volume 'LinuxUDF', timestamp 2022/11/22 14:59 (1000) EXT4-fs (loop2): encrypted files will use data=ordered instead of data journaling mode EXT4-fs (loop2): couldn't mount as ext2 due to feature incompatibilities UDF-fs: error (device loop5): udf_process_sequence: Block 96 of volume descriptor sequence is corrupted or we could not read it