KSTACKOVERFLOW started out with a similar approach and grsecurity users had to find and report the bugs until they changed it for compat...
-
-
-
Not really surprising that upstream took the same kind of approach but as an enabled by default mainline feature it's a different situation.
-
Kernel can't be the one responsible for protection against this because it doesn't control stack setup. (Only for initial thread.)
-
KSTACKOVERFLOW / VMAP_STACK move the kernel stack to virtual memory where they get guard pages, it's not about userspace stack exhaustion.
-
Oh, misread context then. Sorry.
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.