====================================================== WARNING: possible circular locking dependency detected 4.14.153+ #0 Not tainted ------------------------------------------------------ syz-executor.5/5449 is trying to acquire lock: (pmus_lock){+.+.}, at: [<000000005e50533f>] swevent_hlist_get kernel/events/core.c:7896 [inline] (pmus_lock){+.+.}, at: [<000000005e50533f>] perf_swevent_init+0x123/0x4f0 kernel/events/core.c:7956 but task is already holding lock: (&cpuctx_mutex/1){+.+.}, at: [<000000006794b836>] perf_event_ctx_lock_nested+0x15a/0x2d0 kernel/events/core.c:1240 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (&cpuctx_mutex/1){+.+.}: __mutex_lock_common kernel/locking/mutex.c:756 [inline] __mutex_lock+0xf7/0x13e0 kernel/locking/mutex.c:893 mutex_lock_double kernel/events/core.c:9909 [inline] __perf_event_ctx_lock_double kernel/events/core.c:9968 [inline] SYSC_perf_event_open kernel/events/core.c:10233 [inline] SyS_perf_event_open+0x12cf/0x2560 kernel/events/core.c:9988 do_syscall_64+0x19b/0x520 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x42/0xb7 -> #1 (&cpuctx_mutex){+.+.}: __mutex_lock_common kernel/locking/mutex.c:756 [inline] __mutex_lock+0xf7/0x13e0 kernel/locking/mutex.c:893 perf_event_init_cpu+0xa8/0x150 kernel/events/core.c:11231 perf_event_init+0x289/0x2c5 kernel/events/core.c:11278 start_kernel+0x583/0x890 init/main.c:645 secondary_startup_64+0xa5/0xb0 arch/x86/kernel/head_64.S:240 -> #0 (pmus_lock){+.+.}: lock_acquire+0x12b/0x360 kernel/locking/lockdep.c:3994 __mutex_lock_common kernel/locking/mutex.c:756 [inline] __mutex_lock+0xf7/0x13e0 kernel/locking/mutex.c:893 swevent_hlist_get kernel/events/core.c:7896 [inline] perf_swevent_init+0x123/0x4f0 kernel/events/core.c:7956 perf_try_init_event+0xe5/0x200 kernel/events/core.c:9347 perf_init_event kernel/events/core.c:9385 [inline] perf_event_alloc.part.0+0xd13/0x1ff0 kernel/events/core.c:9645 perf_event_alloc kernel/events/core.c:9998 [inline] SYSC_perf_event_open kernel/events/core.c:10105 [inline] SyS_perf_event_open+0x6eb/0x2560 kernel/events/core.c:9988 do_syscall_64+0x19b/0x520 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x42/0xb7 other info that might help us debug this: Chain exists of: pmus_lock --> &cpuctx_mutex --> &cpuctx_mutex/1 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&cpuctx_mutex/1); lock(&cpuctx_mutex); lock(&cpuctx_mutex/1); lock(pmus_lock); *** DEADLOCK *** 2 locks held by syz-executor.5/5449: #0: (&pmus_srcu){....}, at: [<00000000b43b50a3>] perf_event_alloc.part.0+0xb2b/0x1ff0 kernel/events/core.c:9639 #1: (&cpuctx_mutex/1){+.+.}, at: [<000000006794b836>] perf_event_ctx_lock_nested+0x15a/0x2d0 kernel/events/core.c:1240 stack backtrace: CPU: 0 PID: 5449 Comm: syz-executor.5 Not tainted 4.14.153+ #0 Call Trace: __dump_stack lib/dump_stack.c:17 [inline] dump_stack+0xca/0x134 lib/dump_stack.c:53 print_circular_bug.isra.0.cold+0x2dc/0x425 kernel/locking/lockdep.c:1258 check_prev_add kernel/locking/lockdep.c:1901 [inline] check_prevs_add kernel/locking/lockdep.c:2018 [inline] validate_chain kernel/locking/lockdep.c:2460 [inline] __lock_acquire+0x2f5f/0x4320 kernel/locking/lockdep.c:3487 lock_acquire+0x12b/0x360 kernel/locking/lockdep.c:3994 __mutex_lock_common kernel/locking/mutex.c:756 [inline] __mutex_lock+0xf7/0x13e0 kernel/locking/mutex.c:893 swevent_hlist_get kernel/events/core.c:7896 [inline] perf_swevent_init+0x123/0x4f0 kernel/events/core.c:7956 perf_try_init_event+0xe5/0x200 kernel/events/core.c:9347 perf_init_event kernel/events/core.c:9385 [inline] perf_event_alloc.part.0+0xd13/0x1ff0 kernel/events/core.c:9645 perf_event_alloc kernel/events/core.c:9998 [inline] SYSC_perf_event_open kernel/events/core.c:10105 [inline] SyS_perf_event_open+0x6eb/0x2560 kernel/events/core.c:9988 do_syscall_64+0x19b/0x520 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x42/0xb7 RIP: 0033:0x45a219 RSP: 002b:00007f5bfb93ec78 EFLAGS: 00000246 ORIG_RAX: 000000000000012a RAX: ffffffffffffffda RBX: 0000000000000005 RCX: 000000000045a219 RDX: 0000000000000000 RSI: ffffffffffffffff RDI: 0000000020000200 RBP: 000000000075bf20 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000009 R11: 0000000000000246 R12: 00007f5bfb93f6d4 R13: 00000000004c75c7 R14: 00000000004dd348 R15: 00000000ffffffff SELinux: unrecognized netlink message: protocol=4 nlmsg_type=102 sclass=netlink_tcpdiag_socket pig=5645 comm=syz-executor.1 SELinux: unrecognized netlink message: protocol=4 nlmsg_type=102 sclass=netlink_tcpdiag_socket pig=5657 comm=syz-executor.1 SELinux: unrecognized netlink message: protocol=4 nlmsg_type=6 sclass=netlink_tcpdiag_socket pig=5722 comm=syz-executor.1 FAT-fs (loop1): Unrecognized mount option "uid<00000000000000002815" or missing value SELinux: unrecognized netlink message: protocol=4 nlmsg_type=7 sclass=netlink_tcpdiag_socket pig=5920 comm=syz-executor.1 FAT-fs (loop1): bogus number of reserved sectors FAT-fs (loop1): Can't find a valid FAT filesystem FAT-fs (loop1): Unrecognized mount option "uid<00000000000000002815" or missing value FAT-fs (loop1): Unrecognized mount option "uid<00000000000000002815" or missing value FAT-fs (loop1): Unrecognized mount option "uid<00000000000000002815" or missing value FAT-fs (loop1): Unrecognized mount option "uid<00000000000000002815" or missing value FAT-fs (loop1): bogus number of reserved sectors FAT-fs (loop1): Can't find a valid FAT filesystem FAT-fs (loop1): Unrecognized mount option "uid<00000000000000002815" or missing value FAT-fs (loop1): bogus number of reserved sectors FAT-fs (loop1): Can't find a valid FAT filesystem SELinux: unrecognized netlink message: protocol=4 nlmsg_type=0 sclass=netlink_tcpdiag_socket pig=6164 comm=syz-executor.5 SELinux: unrecognized netlink message: protocol=4 nlmsg_type=26159 sclass=netlink_tcpdiag_socket pig=6164 comm=syz-executor.5 SELinux: unrecognized netlink message: protocol=4 nlmsg_type=65535 sclass=netlink_tcpdiag_socket pig=6164 comm=syz-executor.5 SELinux: unrecognized netlink message: protocol=4 nlmsg_type=0 sclass=netlink_tcpdiag_socket pig=6198 comm=syz-executor.5 SELinux: unrecognized netlink message: protocol=4 nlmsg_type=26159 sclass=netlink_tcpdiag_socket pig=6195 comm=syz-executor.5 SELinux: unrecognized netlink message: protocol=4 nlmsg_type=65535 sclass=netlink_tcpdiag_socket pig=6195 comm=syz-executor.5 audit: type=1400 audit(1573511054.634:22): avc: denied { create } for pid=6313 comm="syz-executor.4" scontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023 tcontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023 tclass=netlink_fib_lookup_socket permissive=1 FAT-fs (loop4): Unrecognized mount option "uid<00000000000000002815" or missing value audit: type=1400 audit(1573511054.644:23): avc: denied { write } for pid=6313 comm="syz-executor.4" path="socket:[20987]" dev="sockfs" ino=20987 scontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023 tcontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023 tclass=netlink_fib_lookup_socket permissive=1 FAT-fs (loop4): Unrecognized mount option "uid<00000000000000002815" or missing value audit: type=1400 audit(1573511054.644:24): avc: denied { getattr } for pid=6313 comm="syz-executor.4" path="socket:[20987]" dev="sockfs" ino=20987 scontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023 tcontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023 tclass=netlink_fib_lookup_socket permissive=1 FAT-fs (loop4): Unrecognized mount option "uid<00000000000000002815" or missing value FAT-fs (loop1): Unrecognized mount option "uid<00000000000000002815" or missing value FAT-fs (loop4): Unrecognized mount option "uid<00000000000000002815" or missing value FAT-fs (loop1): Unrecognized mount option "uid<00000000000000002815" or missing value FAT-fs (loop4): bogus number of reserved sectors FAT-fs (loop4): Can't find a valid FAT filesystem SELinux: failed to load policy SELinux: failed to load policy