=============================
WARNING: suspicious RCU usage
5.8.0-rc3-syzkaller #0 Not tainted
-----------------------------
net/tipc/bearer.c:466 suspicious rcu_dereference_check() usage!

other info that might help us debug this:


rcu_scheduler_active = 2, debug_locks = 1
2 locks held by kworker/1:51/2641:
 #0: ffff88812b254538 ((wq_completion)cryptd){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:615 [inline]
 #0: ffff88812b254538 ((wq_completion)cryptd){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:643 [inline]
 #0: ffff88812b254538 ((wq_completion)cryptd){+.+.}-{0:0}, at: process_one_work+0x1de/0x5f0 kernel/workqueue.c:2240
 #1: ffffc900054abe70 ((work_completion)(&cpu_queue->work)){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:615 [inline]
 #1: ffffc900054abe70 ((work_completion)(&cpu_queue->work)){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:643 [inline]
 #1: ffffc900054abe70 ((work_completion)(&cpu_queue->work)){+.+.}-{0:0}, at: process_one_work+0x1de/0x5f0 kernel/workqueue.c:2240

stack backtrace:
CPU: 1 PID: 2641 Comm: kworker/1:51 Not tainted 5.8.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: cryptd cryptd_queue_worker
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0xb3/0xec lib/dump_stack.c:118
 tipc_l2_send_msg+0xef/0x100 net/tipc/bearer.c:466
 tipc_aead_encrypt_done+0x4b/0xc0 net/tipc/crypto.c:761
 cryptd_aead_crypt+0x4f/0xd0 crypto/cryptd.c:739
 cryptd_queue_worker+0x83/0xb0 crypto/cryptd.c:181
 process_one_work+0x26a/0x5f0 kernel/workqueue.c:2269
 worker_thread+0x38/0x380 kernel/workqueue.c:2415
 kthread+0x148/0x170 kernel/kthread.c:291
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:293