grsecurity forums

Hello,

would it possible to release patches for 3.10 until it is marked as EOL by upstream and switch to 3.11 only afterwards?
Early kernels usually contain serious regressions which can lead to instability, bad performance or data loss.
It won't be also good idea to use kernel e.g. 3.10.10 after 3.10.11 will be released because 3.10.11 will likely fix some security bug.

Thanks

I sent this question wrong time as 3.10 will be kernel with long-term support.
Would it be possible this time to release patches for 3.10 until e.g. 3.11.2 or 3.11.3 will be released?

everything's possible of course, you just have to find the right person to do it for you . more seriously, we have already enough on our plates to support yet another kernel series, however briefly. not to mention that you can just keep using the last supported 3.10.x version until you find a switch to 3.11 acceptable. if you want to use 3.10.x+n then in my experience these later versions rarely conflict with our code.

I meant it isn't necessary to support 3.10.x and 3.11.x at same time, but switching of support from 3.10.x to 3.11.x could be done after 3.11.2 or 3.11.3 is released.

well in that sense we already delay the version switch because it takes us time to forward port the patches (during which we still support the previous version) and we're not always ready when 3.x.0 comes out (for 3.11 specifically i already have a patch, but spender doesn't, so grsecurity itself will be delayed). but i don't think we'll want any more artificial delays.