30 Dec
2019
30 Dec
'19
5:44 a.m.
On Mon, Dec 30, 2019 at 04:20:35PM +1100, Aleksa Sarai wrote:
A reasonably detailed explanation of the issues is provided in the patch itself, but the full traces produced by both the oopses and deadlocks is included below (it makes little sense to include them in the commit since we are disabling this feature, not directly fixing the bugs themselves).
I've posted this as an RFC on whether this feature should be allowed at all (and if anyone knows of legitimate uses for it), or if we should work on fixing these other kernel bugs that it exposes.
Umm... Are all of those traces a) reproducible on mainline and b) reproducible as the first oopsen?
As it is, quite a few might be secondary results of earlier memory corruption...