On Mon, 13 Jul 2026 12:16:59 +0900
Masami Hiramatsu (Google) [off-list ref] wrote:

quoted

I also kept this around in case it was needed. Looks like it may be needed.  

Hmm, it's not clear whether this is the result of a scheduling storm
caused by kernel threads. But maybe worth to try.

I don't see what else it could be.

Jeongho, can you try this patch? Or/and you maybe also try using
mlock the LMKD process memory which is passed to trace_marker.

Yes, Jeongho, can you please test this patch and also see if mlocking the
memory used by trace_marker would help too?

-- Steve