============================= WARNING: suspicious RCU usage 4.18.0+ #79 Not tainted ----------------------------- kernel/bpf/core.c:1582 suspicious rcu_dereference_check() usage! other info that might help us debug this: rcu_scheduler_active = 2, debug_locks = 1 2 locks held by syz-executor1/7414: #0: 00000000b1496b9d (&ctx->mutex){+.+.}, at: perf_event_ctx_lock_nested+0x375/0x600 kernel/events/core.c:1276 #1: 00000000f5b11bde (bpf_event_mutex){+.+.}, at: perf_event_query_prog_array+0x1c6/0x380 kernel/trace/bpf_trace.c:1062 stack backtrace: CPU: 1 PID: 7414 Comm: syz-executor1 Not tainted 4.18.0+ #79 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x1c9/0x2b4 lib/dump_stack.c:113 lockdep_rcu_suspicious+0x14a/0x153 kernel/locking/lockdep.c:4562 bpf_prog_array_copy_core+0x2d9/0x360 kernel/bpf/core.c:1582 bpf_prog_array_copy_info+0x9a/0x110 kernel/bpf/core.c:1720 perf_event_query_prog_array+0x22e/0x380 kernel/trace/bpf_trace.c:1063 _perf_ioctl+0x986/0x1600 kernel/events/core.c:5079 perf_ioctl+0x59/0x80 kernel/events/core.c:5110 vfs_ioctl fs/ioctl.c:46 [inline] file_ioctl fs/ioctl.c:500 [inline] do_vfs_ioctl+0x1de/0x1720 fs/ioctl.c:684 ksys_ioctl+0xa9/0xd0 fs/ioctl.c:701 __do_sys_ioctl fs/ioctl.c:708 [inline] __se_sys_ioctl fs/ioctl.c:706 [inline] __x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:706 do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x457089 Code: fd b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 0f 83 cb b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00 RSP: 002b:00007fe3d1e69c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007fe3d1e6a6d4 RCX: 0000000000457089 RDX: 00000000200002c0 RSI: 00000000c008240a RDI: 0000000000000003 RBP: 00000000009300a0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff R13: 00000000004cf478 R14: 00000000004bead0 R15: 0000000000000000 device nr0 entered promiscuous mode can: request_module (can-proto-0) failed. can: request_module (can-proto-0) failed. syz-executor5 (7756) used greatest stack depth: 14936 bytes left nf_conntrack: default automatic helper assignment has been turned off for security reasons and CT-based firewall rule not found. Use the iptables CT target to attach helpers instead. hrtimer: interrupt took 73928 ns EXT4-fs warning (device sda1): ext4_group_add:1636: No reserved GDT blocks, can't resize EXT4-fs warning (device sda1): ext4_group_add:1636: No reserved GDT blocks, can't resize netlink: 3290 bytes leftover after parsing attributes in process `syz-executor3'. netlink: 3290 bytes leftover after parsing attributes in process `syz-executor3'. netlink: 3290 bytes leftover after parsing attributes in process `syz-executor5'. syz-executor3 (8189) used greatest stack depth: 12904 bytes left netlink: 3290 bytes leftover after parsing attributes in process `syz-executor5'. netlink: 3290 bytes leftover after parsing attributes in process `syz-executor5'. netlink: 3290 bytes leftover after parsing attributes in process `syz-executor5'. netlink: 3290 bytes leftover after parsing attributes in process `syz-executor5'. netlink: 3290 bytes leftover after parsing attributes in process `syz-executor5'. netlink: 3290 bytes leftover after parsing attributes in process `syz-executor5'. netlink: 3290 bytes leftover after parsing attributes in process `syz-executor5'. syz-executor5[8360] is installing a program with bpf_probe_write_user helper that may corrupt user memory! syz-executor5[8353] is installing a program with bpf_probe_write_user helper that may corrupt user memory! protocol 88a8 is buggy, dev gre0 protocol 88a8 is buggy, dev gre0