TITLE: WARNING: suspicious RCU usage in gc_worker
TYPE: LOCKDEP

[  388.069210][  T178] =============================
[  388.070602][  T178] WARNING: suspicious RCU usage
[  388.072159][  T178] 5.9.0-12994-gf9893351acae #15 Not tainted
[  388.073462][  T178] -----------------------------
[  388.074687][  T178] kernel/sched/core.c:7264 Illegal context switch in RCU-sched read-side critical section!
[  388.075918][  T178] 
[  388.075918][  T178] other info that might help us debug this:
[  388.075918][  T178] 
[  388.120354][  T178] 
[  388.120354][  T178] rcu_scheduler_active = 2, debug_locks = 1
[  388.122051][  T178] 2 locks held by kworker/u4:4/178:
[  388.123408][  T178]  #0: ffff00004002a138 ((wq_completion)events_power_efficient){+.+.}-{0:0}, at: process_one_work+0x76c/0x1af8
[  388.179802][  T178]  #1: ffff000040ecfd40 ((work_completion)(&(&gc_work->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x76c/0x1af8
[  388.182417][  T178] 
[  388.182417][  T178] stack backtrace:
[  388.183605][  T178] CPU: 1 PID: 178 Comm: kworker/u4:4 Not tainted 5.9.0-12994-gf9893351acae #15
[  388.184315][  T178] Hardware name: linux,dummy-virt (DT)
[  388.185529][  T178] Workqueue: events_power_efficient gc_worker
[  388.186616][  T178] Call trace:
[  388.187209][  T178]  dump_backtrace+0x0/0x4d0
[  388.187731][  T178]  show_stack+0x2c/0x80
[  388.188239][  T178]  dump_stack+0x1b0/0x254
[  388.188785][  T178]  lockdep_rcu_suspicious+0x134/0x14c
[  388.189324][  T178]  ___might_sleep+0x440/0x4d8
[  388.189868][  T178]  gc_worker+0x4bc/0xaa0
[  388.190456][  T178]  process_one_work+0x898/0x1af8
[  388.191026][  T178]  worker_thread+0x3e8/0xc28
[  388.191549][  T178]  kthread+0x30c/0x408
[  388.192118][  T178]  ret_from_fork+0x10/0x30
