I said I understood why spender would be upset about putting a copyright with somebody else's name on grsec code. That's basically all I did
Not sure if it's still up, but back when the patches we're public and support was via forum, every second thread was a new S_O false positive. And they missed obvious ones, like fixing an IPv4 code path without looking at the sibling IPv6 code path.
-
-
An S_O false positive with a broken, obviously untested and unreviewed fix is how I wound up panicking my kernel by pasting a long line of text into my terminal, also reproducible as a tweet-sized local DoS.https://twitter.com/marcan42/status/724745886794833920 …
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.