On 22. Mar 2025, at 16:53, Linus Torvalds torvalds@linux-foundation.org wrote:
We would appreciate any suggestions, such as adding debug messages to the kernel source code, to help us diagnose the root cause.
I think the first thing to do - if you can - is to make sure that a much more *current* kernel actually is ok.
Quick checkin from my side: we’ve been running with this fix for a while now and have been running smoothly on 6.6 for a bit more than 4 months now. We're currently on 6.6.80.
I’ve seen 1 or 2 single reports about blocked tasks that showed folio involvement in the traceback since then, but my status so far is that those were caused by actually blocked IO and both of them recovered cleanly without need of intervention/reboot or any sign of corruption.
When we started diagnosing this we’ve improved our infrastructure to be able to more quickly and safely evaluate new kernel versions. I’ll put a note in to get the migration to 6.12 going and if anything comes up I’ll raise a hand.