upgrade kernels? continued support.

why upgrade from 2.6.24.x to 2.6.25.3?  same reason you would upgrade from 2.6.25.2 to
2.6.25.3.  same reason enterprises pay for Linux.  continued support.

unless someone is backporting security fixes to your current kernel revision, you should
consider doing it yourself or upgrading to 2.6.25.3.  or maybe you've done a risk analysis and
determined that an upgrade to a more recent kernel (2.6.24.x -> 2.6.25.3) is "riskier" (higher
probability of disruption/failure) than a security breach with your current version.

i want to personally thank Oliver Pinter for his continued maintenance of 2.6.22 [1].  the
stable version of linux-vserver is currently stuck at 2.6.22 (due to accommodating the new
container code in later kernels), so i'm forced to stick with 2.6.22 for right now, but
Oliver's "op" patchset has made that a supported possibility.

i only stumbled on his patchset because after the stable team dropped support for 2.6.22, i
searched for Willy Tarreau's patchset because he said he was going to rebase against it [2],
and in desperation i Googled for "2.6.22.20" [3], though i had heard nothing about it while
regularly reading lwn and kerneltrap (but it now appears that i haven't been paying enough
attention to the "Kernel Trees" section of the weekly edition).  i've been compiling his
releases since 2.6.22.21-op1, but honestly i haven't ran one yet because there hasn't been a
pressing enough need, and now that it includes security fixes, i'm waiting for a good time for
"planned downtime" to reboot into the latest.

so consider upgrading to 2.6.25.3 unless a great individual like Oliver Pinter is supporting
2.6.24 (or whatever your version) with backported fixes (security or otherwise).

[1] http://repo.or.cz/w/linux-2.6.22.y-op-patches.git
[2] http://kerneltrap.org/mailarchive/linux-kernel/2007/11/6/...
[3] http://www.google.com/search?q=2.6.22.20