============================= WARNING: suspicious RCU usage 5.12.0-rc4-syzkaller #0 Not tainted ----------------------------- include/linux/skmsg.h:286 suspicious rcu_dereference_check() usage! other info that might help us debug this: rcu_scheduler_active = 2, debug_locks = 1 1 lock held by syz-executor.0/8654: #0: ffff888022a78f88 (clock-AF_INET){++..}-{2:2}, at: sk_psock_drop+0x2c/0x460 net/core/skmsg.c:788 stack backtrace: CPU: 0 PID: 8654 Comm: syz-executor.0 Not tainted 5.12.0-rc4-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:79 [inline] dump_stack+0x141/0x1d7 lib/dump_stack.c:120 sk_psock include/linux/skmsg.h:286 [inline] tcp_bpf_update_proto+0x530/0x5f0 net/ipv4/tcp_bpf.c:504 sk_psock_restore_proto include/linux/skmsg.h:408 [inline] sk_psock_drop+0xdf/0x460 net/core/skmsg.c:789 sk_psock_put include/linux/skmsg.h:446 [inline] tcp_bpf_recvmsg+0x32f/0x480 net/ipv4/tcp_bpf.c:196 inet_recvmsg+0x11b/0x5d0 net/ipv4/af_inet.c:852 sock_recvmsg_nosec net/socket.c:888 [inline] sock_recvmsg net/socket.c:906 [inline] sock_recvmsg net/socket.c:902 [inline] ____sys_recvmsg+0x2c4/0x600 net/socket.c:2569 ___sys_recvmsg+0x127/0x200 net/socket.c:2611 __sys_recvmsg+0xe2/0x1a0 net/socket.c:2641 do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x466459 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 73 01 c3 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fcbcd60e188 EFLAGS: 00000246 ORIG_RAX: 000000000000002f RAX: ffffffffffffffda RBX: 000000000056bf60 RCX: 0000000000466459 RDX: 0000000000000000 RSI: 0000000020005400 RDI: 0000000000000005 RBP: 00000000004bf9fb R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 000000000056bf60 R13: 00007ffedef17a5f R14: 00007fcbcd60e300 R15: 0000000000022000