On 1/16/23 10:12, Steffen Maier wrote:
How would removing this check solve the other and seemingly more fatal
(even without panic_on_warn) WARNING?:
[ 4760.878107] do not call blocking ops when !TASK_RUNNING; state=2 set
at [<000000017ed2c0fa>] __wait_for_common+0xa2/0x240
Isn't the warning address the same for both reports, namely
alua_rtpg_queue+0x3c?
FWIW, it seems we only seem to get such reports for debug kernel builds
(not sure which kconfig options are relevant) but not for production /
performance builds.
Sleep-in-atomic warnings are only reported with kernel debugging
enabled. With kernel debugging disabled, sleeping in atomic context
results in different behavior (kernel hangs).
Thanks,
Bart.
