On Tue, Sep 23, 2025 at 12:30:55PM -0600, Keith Busch wrote: > I don't have a system in this state at the moment, so we checked > previous logs on machines running older kernels. It's extermely > uncommon, but this error was happening prior to this series, so I don't > think this introduced any new problem here. I'll keeping looking, but I > don't think we'll make much progress if I can't find a more reliable > reproducer. Okay, that's great. It needs to get resolved but it is not this series at fault. Very rare is a different perspective, I mis-thought it was happening reproducible all the time.. It seems to me it is actually a legitimate thing for userspace to be able to trigger this cache line debug. If you do concurrent O_DIRECT to the very same memory it should trigger if I read it right.. So it may not even be an actual bug??? Jason
