Comment 2 for bug 1813847

I can see that argument, and also an argument that this isn't a bug at all. That is, the kernel is telling us something strange is happening, but "something strange" is stress-ng's middle name :) That said, these errors combined with a later (and now known to be unrelated) kernel Oops caused me to dig into it. It would be nice if we could somehow prevent this from raising hackles for other users.

Perhaps the kernel's tolerance should be tweaked - that's a policy call for which I lack the expertise to make. Or, perhaps stress-ng could warn that these messages are expected and can be ignored. If nothing else, just having this bug report come up in a Google search will hopefully lessen the impact.