====================================================== WARNING: possible circular locking dependency detected 4.14.307-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.0/12312 is trying to acquire lock: (event_mutex){+.+.}, at: [] ftrace_profile_set_filter+0x64/0x1c0 kernel/trace/trace_events_filter.c:2268 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: -> #4 (&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 -> #3 (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/0x166 init/main.c:1006 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:406 -> #2 (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 -> #1 (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 -> #0 (event_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 ftrace_profile_set_filter+0x64/0x1c0 kernel/trace/trace_events_filter.c:2268 perf_event_set_filter kernel/events/core.c:8729 [inline] _perf_ioctl+0x12b3/0x1a60 kernel/events/core.c:4852 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_mutex --> pmus_lock --> &cpuctx_mutex Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&cpuctx_mutex); lock(pmus_lock); lock(&cpuctx_mutex); lock(event_mutex); *** DEADLOCK *** 1 lock held by syz-executor.0/12312: #0: (&cpuctx_mutex){+.+.}, at: [] perf_event_ctx_lock_nested+0x14d/0x2c0 kernel/events/core.c:1241 stack backtrace: CPU: 0 PID: 12312 Comm: syz-executor.0 Not tainted 4.14.307-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/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 ftrace_profile_set_filter+0x64/0x1c0 kernel/trace/trace_events_filter.c:2268 perf_event_set_filter kernel/events/core.c:8729 [inline] _perf_ioctl+0x12b3/0x1a60 kernel/events/core.c:4852 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:0x7f1d890f20f9 RSP: 002b:00007f1d87664168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f1d89211f80 RCX: 00007f1d890f20f9 RDX: 0000000020000040 RSI: 0000000040082406 RDI: 0000000000000003 RBP: 00007f1d8914dae9 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffc29fb9dbf R14: 00007f1d87664300 R15: 0000000000022000 netlink: 192 bytes leftover after parsing attributes in process `syz-executor.5'. netlink: 200 bytes leftover after parsing attributes in process `syz-executor.0'. netlink: 200 bytes leftover after parsing attributes in process `syz-executor.0'. netlink: 200 bytes leftover after parsing attributes in process `syz-executor.0'. netlink: 192 bytes leftover after parsing attributes in process `syz-executor.3'. netlink: 200 bytes leftover after parsing attributes in process `syz-executor.0'. RDS: rds_bind could not find a transport for 172.20.20.187, load rds_tcp or rds_rdma? EXT4-fs (sda1): Unrecognized mount option "fd=0xffffffffffffffff" or missing value netlink: 64 bytes leftover after parsing attributes in process `syz-executor.1'. EXT4-fs (sda1): re-mounted. Opts: (null) hfsplus: failed to load extents file NILFS (loop1): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds NILFS (loop0): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds NILFS (loop2): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds hfsplus: failed to load extents file hfsplus: failed to load extents file BTRFS: device fsid 24c7a497-3402-47dd-bef8-82358f5f30e0 devid 1 transid 8 /dev/loop4 BTRFS info (device loop4): turning off barriers BTRFS info (device loop4): use zlib compression BTRFS info (device loop4): turning on barriers BTRFS info (device loop4): max_inline at 14 BTRFS info (device loop4): turning on discard BTRFS info (device loop4): using free space tree BTRFS info (device loop4): has skinny extents BTRFS info (device loop4): turning off barriers BTRFS info (device loop4): use zlib compression BTRFS info (device loop4): turning on barriers BTRFS info (device loop4): max_inline at 14 BTRFS info (device loop4): turning on discard BTRFS info (device loop4): using free space tree BTRFS info (device loop4): has skinny extents EXT4-fs (loop0): Journaled quota options ignored when QUOTA feature is enabled EXT4-fs: Warning: mounting with data=journal disables delayed allocation and O_DIRECT support! EXT4-fs (loop0): feature flags set on rev 0 fs, running e2fsck is recommended EXT4-fs warning (device loop0): ext4_update_dynamic_rev:793: updating to rev 1 because of new feature flag, running e2fsck is recommended [EXT4 FS bs=2048, gc=1, bpg=16384, ipg=32, mo=8002c01c, mo2=0002] __quota_error: 2 callbacks suppressed Quota error (device loop0): v2_read_header: Failed header read: expected=8 got=0 EXT4-fs warning (device loop0): ext4_enable_quotas:5780: Failed to enable quota tracking (type=-1, err=-22). Please run e2fsck to fix. unregister_netdevice: waiting for ip6gre0 to become free. Usage count = -1 EXT4-fs (loop0): mount failed BTRFS info (device loop4): turning off barriers BTRFS info (device loop4): use zlib compression BTRFS info (device loop4): turning on barriers BTRFS info (device loop4): max_inline at 14 BTRFS info (device loop4): turning on discard BTRFS info (device loop4): using free space tree BTRFS info (device loop4): has skinny extents attempt to access beyond end of device loop0: rw=2049, want=1041, limit=128