Unreviewed code in 3.11

Posted Aug 8, 2013 11:38 UTC (Thu) by jezuch (subscriber, #52988)
Parent article: Unreviewed code in 3.11

> The problem is, for most of these are, yet again, lots of small bits scattered around the place without any real overall theme to them.

And:

> Tell me how I can put this stuff into -next _and_ keep it secret because it's security related.

That reminds me of Spender's crusade against kernel maintainers lying about security impact of patches. This "secrecy" is really off-putting (and a nice attack vector for someone wanting to slip in a backdoor, or something).

Unreviewed code in 3.11

Posted Aug 14, 2013 15:44 UTC (Wed) by prometheanfire (subscriber, #65683) [Link]

It is off-putting. I don't know a method of getting the fix out before the bug becomes public though... I wonder if I would feel better if they said what the security issue/bug/commit was 1 month after the fix is committed to git.