OpenSUSE kernel news – 11.09.2010

Posted: September 5, 2010 in kernel, OpenSUSE

Hello, people, and welcome! In this week’s news….

-Geert Uytterhoeven published a list that might interest a lot of people : a summary containing
the differences between .35 and .36-rc3; the detailed summary can be found here :
http://www.kernel.org/pub/linux/kernel/people/geert/linux-log/v2.6.36-rc3.summary.gz .

-Takashi Iwai has some sound fixes (“Two USB-audio fixes and one HD-audio quirk.”) in a pull
request for -rc4, Junio Hamano announced a maintenance release for Git, Greg Kroah-Hartman
released fixes for the USB, sys, tty and staging trees and finally Subrata Modak announced a
fresh release of the LTP project (the August edition) – you can read the last two months’ changes
here : http://ltp.git.sourceforge.net/git/gitweb.cgi?p=ltp/ltp-dev.git;a=commitdiff;h=63bb9536f66b8117a723e99149ee8091dcae4fad .

-Ryusuke Konishi updated the nilfs2 git tree with a leak issue fix, Artem Bityutskiy has
updates for the UBI tree, Michael S. Tsirkin of Redhat posted some regression fixes for
vhost and Dave Airlie has a pull request concerning DRI :
“radeon + nouveau + a couple of core fixes. Important radeon evergreen fix,
which allows accel to run without locking up the gpu, also a fix for
r700 AGP, and a couple of bkl removal fixes for nouveau.”

-In an e-mail titled “Linux 2.4.37.10 + 2.4 EOL plans”, Willy Tarreau, as the title suggests, announces
a new fix release for kernel 2.4, as well as intentions to end further updates. Here’s a part of the announcement :
“This is the 10th fixup release of kernel 2.4.37. Most changes concern
relatively minor issues as well as a few medium security issues affecting
some specific areas (sctp, irda, jfs). Most likely, very few people are
concerned. The full (still short) changelog is provided at the end of this
mail.

Some of you have noticed that the last update was released 7 months ago.
This is long, but these days, very few of the issues reported on 2.6 also
affect 2.4, so basically the number of bug reports on 2.4 fades out quite
fast. Also, I generally prefer not to release a kernel just for a single
non-critical patch, especially if we consider that 2.4 users generally
wait a few weeks to a few months before upgrading. Since quite a bunch of
fixes started to pile up, I thought it was time to release a new one.

I’ve realized that I only have a few 2.4-based systems left in production,
and that my other systems are now running fine with long-term supported
2.6.27 and 2.6.32 kernels. At my company, we’re still shipping our load
balancers with a 2.4 kernel, but we’re considering upgrading to 2.6 for a
next release, so even there I won’t have many reasons to work on 2.4. All
these clues should ring a bell for those of you still relying on 2.4…

So what I’m planning to do for next releases is to automatically stop
providing updates one year after the last update. What this means is that
if there are important fixes to merge, they will shift the end of support
date for one new year, but if nothing important happens during one whole
year, that proves the code is stable enough to fly by itself, and you don’t
need any update anymore. This is not a rigid rule though and I still decide
whether something has to be fixed or not. If I collect some non-important
patches, I’ll queue them up but not emit a release for them. If something
critical happens, then I’ll emit a new release. If that happens after one
year of silence, it is possible that I’ll still emit a release, without
shifting the end of life date further.”

-An XFS update via a git pull request is announced by Alex Elder, while Ingo Molnar
released patches for the core and x86 trees; also, Roland Dreier has a few fixes for Infiniband,
Jeff Garzik requested a git pull for libata plus updates for the perf and tracing trees by their
respective authors.

-In other news, Takashi Iwai updated sound and Marcello Tosatti updated kvm (2.6.36-rc3), aaand…
that’s all for this week’s edition of OpenSUSE kernel news! Have a good weekend and see ya!

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s