Sounds like more of a risk for production environments than mobile then.
grsec's is x86 only, in 2 parts: thread_info move & vmap stack. upstream has both on x86 and former on arm64 & s390
-
-
the NIH'd version of vmap stack is full of bugs, still a whack-a-mole game a few releases later.
-
Understood. There are many paths to getting things into upstream and stabilization can be one of the costs.
-
IMHO bugs due to entirely avoidable design errors (NIH) are simply irresponsible and bad engineering.
-
As you know, the way to change upstream Linux kernel engineering practices is to participate directly :)
-
pointless when stuff like __ro_after_init and now refcount_t can go in despite being bad engineering...
-
I don't share your "bad engineering" opinion, and I think your involvement wouldn't be pointless at all.
-
i did discuss those two (mis)features at the time to no avail. guess we just have different standards ;).
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.