Re: Stable kernel tree status, January 18, 2010

From: Willy Tarreau
Date: Tue Jan 19 2010 - 17:40:00 EST

On Mon, Jan 18, 2010 at 11:09:39AM -0800, Greg KH wrote:
> Here's the state of the -stable kernel trees, as of January 18, 2010.
> 2.6.27-stable
> The 2.6.27-stable kernel tree is still living on, as a "long-term"
> stable release. But, I do have to warn users of this tree, the older it
> gets, the less viable it becomes. Not all bugfixes are being backported
> to this kernel version due to massive code changes in the over 2 years
> since this kernel has been released. I am doing my best to backport
> fixes that I become aware of, and I encourage anyone who does fix any
> types of bugs in the main kernel tree to let me know if the change
> should be applied to this older kernel version.
> I'll probably keep maintaining it for at least 6-8 more months, but
> after that, I can not guarantee it's viability. Note, one other
> developer has volunteered to pick up the tree after I am finished with
> it, but I can not speak for him at this time.

I can confirm that I proposed to Greg to take it up to give time to
users to switch to newer releases. BUT it is important to understand
that it will then considerably slow down, basically just like 2.4,
with one release every few months when a major issue has to be fixed.
This is simply because I cannot spend as much time as Greg on that
task. Right now I pick most of the 2.4 fixes from Greg's patches that
I backport, so that should not change much with another kernel. However
Greg's rule above still applies : if a fix cannot easily be backported,
better drop it than break everything else.

For this reason, the kernel will eventually become obsolete, and
everyone should consider migrating to 2.6.32-stable.

BTW, thanks Greg for doing that again with 2.6.32. I hope that your
early announcement will incite more people to adopt it so that many
regressions are quickly spotted and fixed.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at