4 ms·
IMHO, RHEL kernels should never be considered stable or production-ready. Sadly, support contracts sometimes require their use.
by peterwwillis 13y ago
IMHO, RHEL kernels should never be considered stable or production-ready. Sadly, support contracts sometimes require their use.
- otterley 13y agoOn what basis is your opinion founded? Most of the top websites in the world use RHEL or one of its brethren (aside from Google).
- peterwwillis 13y agoYeah, and they use it mainly due to support contracts and industry certifications. Doesn't make it a good idea. They used to release RHEL kernels with hundreds of patches that could be applied in line, or removed/fixed individually. Now they keep one tree that they manage privately and release only the fully-patched source, without any documentation about what's changed or why. Your only hope of figuring out what has been changed or getting help in fixing it is to pay for support, or browse the commits at Oracle's RedPatch (https://oss.oracle.com/git/?p=redpatch.git https://oss.oracle.com/git/?p=redpatch.git). Basically, a RHEL kernel is an obscure product designed to make them money. The primary reason RHEL kernels aren't stable is the bug this thread is about. There is no valid reason to backport a change to swappiness behavior into a 'stable' kernel. The whole idea behind 'stable' is it works, so don't change it. But RHEL has other ideas. RHEL kernels are more likely to contain security holes than a vanilla kernel of the same version, partially due to the backporting of new or changing functionality. They also don't get as much testing and scrutiny as the vanilla tree. Besides internal testing, changes that aren't included in stock linux kernels are introduced into Fedora for their users to beta-test. Over time we've seen plenty of security holes make it into otherwise 'stable' RHEL kernels and tools by RHEL backports. It's usually a feature they're importing that brings along with it additional attack surface, or introduces a hole in pre-existing functionality. It's also a big pain in the ass to get a RHEL kernel to support something a normal kernel would support, due to the major changes. You also have to modify whatever patches you want to apply on top of RHEL since most people create patches targeting the vanilla tree and not RHEL. In general if you have a problem with the RHEL kernel you have a lot better chance of success by throwing it out and downloading a vanilla kernel. At this point RHEL's kernel is a nightmare hybrid of changes going into a tree that nobody else uses because they've moved to 3.x trees for new enterprise releases. Between vanilla 2.6.32 and RHEL's 2.6.32-431 there are 9144 files changed, 3,563,927 insertions, 699,721 deletions. The diff is 45MB compressed. The RHEL sources are 102 megabytes larger than the vanilla source. And in case anyone asks, no, this swappiness change was not introduced into the vanilla kernel's long-term support tree (which is still maintained for this same kernel version). (http://www.kroah.com/log/linux/2.6.32-stable.html http://www.kroah.com/log/linux/2.6.32-stable.html)
- otterley 13y agoI get what you're saying, but none of this (except for your contention about introducing security issues via backported patches) has anything to do with its _reliability_, which is what most people would interpret "stability" or "production readiness" to mean. As for your specific contention about the stability or security of backported patches -- can you provide a citation that RHEL kernels have any more fixes per year than, say, Ubuntu kernels? (Which BTW have their own backported patches.)
- peterwwillis 13y agoThe posted article is about a backported feature that changed expected behavior and killed mysql processes. That is literally instability introduced by a backported patch. The security/stability problems in backported features speak for themselves; you don't get bugs in features that don't exist. I'm not making an argument about who has more changes. RHEL just has bad changes. Bad because they're changing expected functionality. Bad because they're introducing unnecessary features. Bad because they increase exposure to security and stability bugs. Bad because their changes aren't documented publicly. Bad because they keep trying to support an antiquated platform that every other enterprise has moved on from. Bad because it's much more difficult to modify, and includes less support for modern hardware (unless it's patched in, again increasing problems). Bad because they have less testing and review. Bad because it creates vendor lock-in. I can't actually think of a single good reason to use a RHEL kernel, other than the vendor-locked-in support contracts and industry certifications that use RHEL as a standard.
- otterley 13y agoI respectfully disagree that you can come to such a conclusion from a single example (especially since this change was also introduced into the mainline). I think the benefits of RHEL, including its excellent record of long-term support, outweigh minor occasional trip-ups like this.
- bri3d 13y agoI don't think this issue has much to do with Red Hat kernel specifically - that commit has been in the mainline kernel since 3.5.
- mmmooo 13y agowell redhat back ported it to their 2.6.x kernels, which, one could consider, can cause a giant regression due to a minor kernel patch (assuming you are using swappiness=0). As said by others, swappiness=0 isn't as great an idea as some people claim in the first place.
- josho 13y agoI don't follow Red Hat all that closely anymore, but they have had a long standing policy of back porting changes to kernels. In fact, this is part of why they've been successful in enterprise: RH provides long term support on a stable kernel that receives key fixes from upstream kernel versions.
- Sanddancer 13y agoThe problem is that this wasn't a bug fix, but a behavior change. Worse, it's an undocumented behavior change. This is the sort of thing that can and should be documented.
- mmmooo 13y agoYep, and/or not back-ported.