============================= WARNING: suspicious RCU usage 5.9.0-rc1-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/0:4/8140: #0: ffff88821ae22938 ((wq_completion)cryptd){+.+.}-{0:0}, at: process_one_work+0x6f4/0xfc0 kernel/workqueue.c:2242 #1: ffffc90015d9fd80 ((work_completion)(&cpu_queue->work)){+.+.}-{0:0}, at: process_one_work+0x733/0xfc0 kernel/workqueue.c:2244 stack backtrace: CPU: 0 PID: 8140 Comm: kworker/0:4 Not tainted 5.9.0-rc1-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+0x1f0/0x31e lib/dump_stack.c:118 tipc_l2_send_msg+0x2f7/0x3a0 net/tipc/bearer.c:466 tipc_aead_encrypt_done+0x1b8/0x2c0 net/tipc/crypto.c:761 cryptd_aead_crypt+0xfd/0x1e0 crypto/cryptd.c:739 cryptd_queue_worker+0xed/0x170 crypto/cryptd.c:181 process_one_work+0x789/0xfc0 kernel/workqueue.c:2269 worker_thread+0xaa4/0x1460 kernel/workqueue.c:2415 kthread+0x37e/0x3a0 drivers/block/aoe/aoecmd.c:1234 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294