Hello Honza,
Just want to make sure this does not get lost - as mentioned earlier,
reverting 51ae846cff5 leads to a kernel build that does not have this issue.
Yes, I'm aware of this and still cannot quite wrap my head how it could be
given the stacktraces I see :) They do not seem to come anywhere near that
code...
Just reaching out to let folks know that we see more reports on this
issue coming in for kernels >=5.15.63, see
https://github.com/flatcar/Flatcar/issues/847#issuecomment-1286523602.
Best regards,
Thilo
