Skip to contentSkip to conversation

Linux 2.6.27

DISCUSSION Linus Torvalds 13 participants 20 messages Oct 10, 2008 – Nov 14, 2008

lore
Share & tools
lore
#0 lore raw

So not a lot happened after -rc9, which is mostly good. I certainly don't want to have any upheavals at the end of an -rc series, although I wouldn't have minded more people looking at the regression list. That said, I think we're in pretty good shape, and it's not like I can hold back releases indefinitely anyway.

The shortlog from -rc9 really is small, and I doubt many people will notice the changes. And as usual, if you want to know about the big changes since 2.6.26, the full ChangeLog is available, but people are much better off with the human-readable explanations at

http://kernelnewbies.org/LinuxChanges

but most important is obviously to just test it. Especially if you've been a bad boy (or girl) and haven't been testing the -rc's.

Linus

---
Ali Saidi (1):
tcp: Fix possible double-ack w/ user dma

Alistair John Strachan (2):
hwmon: (abituguru3) Enable reading from AUX3 fan on Abit AT8 32X
hwmon: (abituguru3) Enable DMI probing feature on Abit AT8 32X

Corentin Chary (1):
eeepc-laptop: Fix hwmon interface

Daniele Lacamera (1):
tcp: Fix tcp_hybla zero congestion window growth with small rho and large cwnd.

Darrick J. Wong (2):
hwmon: Define sysfs interface for energy consumption register
hwmon: (adt7473) Fix some bogosity in documentation file

David S. Miller (2):
Revert "ax25: Fix std timer socket destroy handling."
ax25: Quick fix for making sure unaccepted sockets get destroyed.

Herbert Xu (1):
net: Fix netdev_run_todo dead-lock

Jarek Poplawski (1):
netrom: Fix sock_orphan() use in nr_release

Jean Delvare (1):
hwmon: (it87) Prevent power-off on Shuttle SN68PT

Linus Torvalds (3):

      Revert "V4L/DVB (8904): cx88: add missing unlock_kernel"
      Don't allow splice() to files opened with O_APPEND
      Linux 2.6.27

Marcel Holtmann (3):
[Bluetooth] Fix double frees on error paths of btusb and bpa10x drivers [Bluetooth] Add reset quirk for new Targus and Belkin dongles [Bluetooth] Add reset quirk for A-Link BlueUSB21 dongle

Matt Mackall (2):
SLOB: fix bogus ksize calculation
SLOB: fix bogus ksize calculation fix

Németh Márton (1):
[CPUFREQ] correct broken links and email addresses

Patrick McHardy (1):

      net: only invoke dev->change_rx_flags when device is UP

Ralf Baechle (1):
[MIPS] Sibyte: Register PIO PATA device only for Swarm and Litte Sur

#1 lore raw

Linux 2.6.27 will be a longtime supported kernel

2.6.16 has become a bit dated, and I'll maintain 2.6.27 for a few years as a replacement.

As with 2.6.16, I'll pickup maintainance when the normal -stable maintainance ends (at some point after 2.6.28 gets released in January).

It is intended to fill the niche for users who are not using distribution kernels but want to use a regression-free kernel for a longer time. It might be a small part of the userbase, but after the experiences with 2.6.16 I can say that there are quite a few users who appreciate such an offering.

As people might have noted I wasn't able to do much kernel stuff recently, and 2.6.16 also suffered from this. I'll bring 2.6.16 back into shape and keep it maintained until at least mid-2009.

cu
Adrian

Signature · 4 lines
       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed
#2 lore raw

Re: [stable] Linux 2.6.27 will be a longtime supported kernel

Quoted 2 lines · Adrian Bunk

2.6.16 has become a bit dated, and I'll maintain 2.6.27 for a few years as a replacement.

Hm, you're not the only one going to be doing this, there are at least three distros basing their latest releases on this kernel :)

Quoted 2 lines

As with 2.6.16, I'll pickup maintainance when the normal -stable maintainance ends (at some point after 2.6.28 gets released in January).

I was considering hanging on to .27 for a while longer than the .28 release, much like .25 has been working out. But probably some time after .29 I'll be glad to hand it off to you for you to maintain like .16 was. Is that ok?

Quoted 5 lines

It is intended to fill the niche for users who are not using distribution kernels but want to use a regression-free kernel for a longer time. It might be a small part of the userbase, but after the experiences with 2.6.16 I can say that there are quite a few users who appreciate such an offering.

Hey, I personally liked it as it made maintaining SLES a lot easier, thanks a lot for your work there!

thanks,

greg k-h

#3 lore raw

Re: [stable] Linux 2.6.27 will be a longtime supported kernel

Quoted 10 lines · Greg KH

On Sun, Oct 12, 2008 at 12:03:40AM +0300, Adrian Bunk wrote:
...

Quoted 2 lines

As with 2.6.16, I'll pickup maintainance when the normal -stable maintainance ends (at some point after 2.6.28 gets released in January).

I was considering hanging on to .27 for a while longer than the .28 release, much like .25 has been working out. But probably some time after .29 I'll be glad to hand it off to you for you to maintain like .16 was. Is that ok?
...

Sure - I don't want to disturb the normal -stable maintainance, and whenever you stop maintaining 2.6.27 I'll pick it up.

Quoted 3 lines

thanks,

greg k-h

cu
Adrian

Signature · 4 lines
       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed
#4 lore raw

Re: [stable] Linux 2.6.27 will be a longtime supported kernel

In reply to Greg KH
Quoted 6 lines · Greg KH
Quoted 2 lines · Adrian Bunk

2.6.16 has become a bit dated, and I'll maintain 2.6.27 for a few years as a replacement.

Hm, you're not the only one going to be doing this, there are at least three distros basing their latest releases on this kernel :)

Oh that's good news as it will give it more exposure and bugs will be found and fixed faster. Having 2.6.25 in opensuse may have contributed to its stability.

Quoted 5 lines
Quoted 2 lines

As with 2.6.16, I'll pickup maintainance when the normal -stable maintainance ends (at some point after 2.6.28 gets released in January).

I was considering hanging on to .27 for a while longer than the .28 release, much like .25 has been working out.

BTW, how long to you think you'll keep pushing fixes for .25 ? It's been working really well and might have been the most reliable 2.6 I've seen, 2.6.16 aside. I'll keep using it waiting for 2.6.27 to settle down a bit.

Quoted 2 lines

Hey, I personally liked it as it made maintaining SLES a lot easier, thanks a lot for your work there!

Not only there, but everywhere you need to embed a 2.6 without too many features and without an easy ability to upgrade it, 2.6.16 has been a good choice.

Thanks to you guys for the time you spend maintaining stable releases! I really hope that 2.6.27 will be a viable replacement for 2.4 in the long term.

Willy

#5 lore raw

Re: Linux 2.6.27 will be a longtime supported kernel

In reply to Adrian Bunk
Quoted 12 lines · Adrian Bunk

2.6.16 has become a bit dated, and I'll maintain 2.6.27 for a few years as a replacement.

As with 2.6.16, I'll pickup maintainance when the normal -stable maintainance ends (at some point after 2.6.28 gets released in January).

It is intended to fill the niche for users who are not using distribution kernels but want to use a regression-free kernel for a longer time. It might be a small part of the userbase, but after the experiences with 2.6.16 I can say that there are quite a few users who appreciate such an offering.

Quoted 3 lines

As people might have noted I wasn't able to do much kernel stuff recently, and 2.6.16 also suffered from this. I'll bring 2.6.16 back into shape and keep it maintained until at least mid-2009.

Thanks for your work.

I am just wondering why you only selected .16 and .27, not others? Are there some specical reasons why you did this?

Thank you.

Signature · 1 line
"Sometimes the only way to stay sane is to go a little crazy."
#6 lore raw

Re: Linux 2.6.27 will be a longtime supported kernel

Quoted 13 lines · Américo Wang
Quoted 12 lines · Adrian Bunk

2.6.16 has become a bit dated, and I'll maintain 2.6.27 for a few years as a replacement.

As with 2.6.16, I'll pickup maintainance when the normal -stable maintainance ends (at some point after 2.6.28 gets released in January).

It is intended to fill the niche for users who are not using distribution kernels but want to use a regression-free kernel for a longer time. It might be a small part of the userbase, but after the experiences with 2.6.16 I can say that there are quite a few users who appreciate such an offering.

Quoted 8 lines
Quoted 3 lines

As people might have noted I wasn't able to do much kernel stuff recently, and 2.6.16 also suffered from this. I'll bring 2.6.16 back into shape and keep it maintained until at least mid-2009.

Thanks for your work.

I am just wondering why you only selected .16 and .27, not others? Are there some specical reasons why you did this?

If the question is why it isn't .26 or .28:

I'm checking whether my computer works fine with a kernel, and also very slightly what distributions might use a kernel, but in the end it's pretty random.

If the question is about the big gap between them:

I don't want to maintain 10 kernels at once, and also for getting fixes from other kernel developers it's better when I don't do this for too many kernels.

Quoted 1 line

Thank you.

cu
Adrian

Signature · 4 lines
       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed
#7 lore raw

Re: Linux 2.6.27 will be a longtime supported kernel

Quoted 5 lines · Adrian Bunk

If the question is why it isn't .26 or .28:

I'm checking whether my computer works fine with a kernel, and also very slightly what distributions might use a kernel, but in the end it's pretty random.

So any distributions using .27 by the looks of it? It looks like Debian is going with .26 for the 5.0 release, so if nothing else they will have to be maintaining that one for quite a while. I suppose having someone maintain .27 makes sense in that case.

Signature · 1 line
Len Sorensen
#8 lore raw

Re: [stable] Linux 2.6.27 will be a longtime supported kernel

Quoted 11 lines · Lennart Sorensen
Quoted 5 lines · Adrian Bunk

If the question is why it isn't .26 or .28:

I'm checking whether my computer works fine with a kernel, and also very slightly what distributions might use a kernel, but in the end it's pretty random.

So any distributions using .27 by the looks of it? It looks like Debian is going with .26 for the 5.0 release, so if nothing else they will have to be maintaining that one for quite a while. I suppose having someone maintain .27 makes sense in that case.

Fedora, Ubuntu, and openSUSE are going to be based on .27 from what I can tell.

thanks,

greg k-h

#9 lore raw

Re: [stable] Linux 2.6.27 will be a longtime supported kernel

Quoted 2 lines · Greg KH

Fedora, Ubuntu, and openSUSE are going to be based on .27 from what I can tell.

opensuse 10.3 is 2.6.22
opensuse 11 is 2.6.25
so opensuse 12 will be 2.6.27? it is supposed to use 2.6.28, right?

YH

#10 lore raw

Re: [stable] Linux 2.6.27 will be a longtime supported kernel

Quoted 5 lines · Yinghai Lu
Quoted 2 lines

Fedora, Ubuntu, and openSUSE are going to be based on .27 from what I can tell.

opensuse 10.3 is 2.6.22
opensuse 11 is 2.6.25
so opensuse 12 will be 2.6.27? it is supposed to use 2.6.28, right?

FWIW -- opensuse 12 is out of question right now. 11.1 is the upcoming release (based on 2.6.27).

Signature · 1 line
Jiri Kosina
#11 lore raw

Re: [stable] Linux 2.6.27 will be a longtime supported kernel

In reply to Yinghai Lu
Quoted 8 lines · Yinghai Lu
Quoted 2 lines · Greg KH

Fedora, Ubuntu, and openSUSE are going to be based on .27 from what I can tell.

opensuse 10.3 is 2.6.22
opensuse 11 is 2.6.25
so opensuse 12 will be 2.6.27? it is supposed to use 2.6.28, right?

openSUSE 11.1 will be 2.6.27. As it is to be released pretty soon now, it would be a bit hard to base it off of .28 which isn't even out yet :)

thanks,

greg k-h

#12 lore raw

Re: [stable] Linux 2.6.27 will be a longtime supported kernel

In reply to Greg KH
Quoted 9 lines · Greg KH
Quoted 7 lines · Lennart Sorensen
Quoted 4 lines · Adrian Bunk

If the question is why it isn't .26 or .28:

I'm checking whether my computer works fine with a kernel, and also very slightly what distributions might use a kernel, but in the end it's pretty random.

Quoted 8 lines
Quoted 4 lines

So any distributions using .27 by the looks of it? It looks like Debian is going with .26 for the 5.0 release, so if nothing else they will have to be maintaining that one for quite a while. I suppose having someone maintain .27 makes sense in that case.

Fedora, Ubuntu, and openSUSE are going to be based on .27 from what I can tell.

According to distrowatch, Mandriva and Gentoo as well.

Chris

#13 lore raw

Re: [stable] Linux 2.6.27 will be a longtime supported kernel

Quoted 10 lines · Chris Friesen
Quoted 9 lines · Greg KH
Quoted 8 lines · Lennart Sorensen
Quoted 5 lines · Adrian Bunk

If the question is why it isn't .26 or .28:

I'm checking whether my computer works fine with a kernel, and also very slightly what distributions might use a kernel, but in the end it's pretty random.

Quoted 8 lines
Quoted 6 lines
Quoted 4 lines

So any distributions using .27 by the looks of it? It looks like Debian is going with .26 for the 5.0 release, so if nothing else they will have to be maintaining that one for quite a while. I suppose having someone maintain .27 makes sense in that case.

Fedora, Ubuntu, and openSUSE are going to be based on .27 from what I can tell.

According to distrowatch, Mandriva and Gentoo as well.

Gentoo always uses whatever is released, once .28 is out, it will switch to that after a short while :)

thanks,

greg k-h

#14 lore raw

Re: Linux 2.6.27 will be a longtime supported kernel

In reply to Adrian Bunk
Quoted 5 lines · Adrian Bunk

It is intended to fill the niche for users who are not using distribution kernels but want to use a regression-free kernel for a longer time. It might be a small part of the userbase, but after the experiences with 2.6.16 I can say that there are quite a few users who appreciate such an offering.

Your work is very much appreciated, we use 2.6.16 extensively and are moving to base things off 2.6.27 for the future. It's nice to know it'll be supported for the foreseeable future.

++

#15 lore raw

Re: Linux 2.6.27 will be a longtime supported kernel

Quoted 10 lines · Alex Howells
Quoted 5 lines · Adrian Bunk

It is intended to fill the niche for users who are not using distribution kernels but want to use a regression-free kernel for a longer time. It might be a small part of the userbase, but after the experiences with 2.6.16 I can say that there are quite a few users who appreciate such an offering.

Your work is very much appreciated, we use 2.6.16 extensively and are moving to base things off 2.6.27 for the future. It's nice to know it'll be supported for the foreseeable future.

Agreed, I think it is very useful work for many consumers of the kernel.

#16 lore raw

Re: Linux 2.6.27 will be a longtime supported kernel

In reply to Adrian Bunk
Quoted 1 line · Adrian Bunk

2.6.16 has become a bit dated, and I'll maintain 2.6.27 for a few years as a replacement.

Consider this another "thank you" for the work that you and also the -stable team are doing.

For various reasons (long release cycles, long-term support contracts, etc.) the release-early/often model can be difficult. These periodic longer-term kernels are very useful.

Chris

#17 lore raw
In reply to Linus Torvalds
Quoted 7 lines · Linus Torvalds

So not a lot happened after -rc9, which is mostly good. I certainly don't want to have any upheavals at the end of an -rc series, although I wouldn't have minded more people looking at the regression list. That said, I think we're in pretty good shape, and it's not like I can hold back releases indefinitely anyway.

The shortlog from -rc9 really is small, and I doubt many people will notice the changes. And as usual, if you want to know about the big changes since 2.6.26, the full ChangeLog is available, but people are much better off with the human-readable explanations at

http://kernelnewbies.org/LinuxChanges

It seems redundant to have the table of contents include links which point back to the line containing the link. Ex: Clicking on the "3 network" link in "8 drivers" takes you back to the link with that link, not to the description which you find by scrolling down to the entry you want. Perhaps not worth doing at all.

The description is fine, just unintuitive to use, most documents have a contents click take you to the material you wnat to read...

And the athl1e driver seems to work really well, I've been running the -rc7 with that network, PAE, and heavily using KVM without any problems to report. Another good job.

Signature · 3 lines
Bill Davidsen <[email protected]>
  "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot
#18 lore raw
Quoted 6 lines · Bill Davidsen
Quoted 2 lines

http://kernelnewbies.org/LinuxChanges

It seems redundant to have the table of contents include links which point back to the line containing the link. Ex: Clicking on the "3 network" link in "8 drivers" takes you back to the link with that link, not to the description which you find by scrolling down to the entry you want.

The anchors at the LinuxChanges page are wrong.
Try http://kernelnewbies.org/Linux_2_6_27 .

Signature · 3 lines
Stefan Richter
-=====-==--- =-== -===-
http://arcgraph.de/sr/
#19 lore raw
Quoted 5 lines · Stefan Richter
Quoted 3 lines · Bill Davidsen
Quoted 3 lines

http://kernelnewbies.org/LinuxChanges

Quoted 9 lines
Quoted 5 lines

It seems redundant to have the table of contents include links which point back to the line containing the link. Ex: Clicking on the "3 network" link in "8 drivers" takes you back to the link with that link, not to the description which you find by scrolling down to the entry you want.

The anchors at the LinuxChanges page are wrong.
Try http://kernelnewbies.org/Linux_2_6_27 .

Thank you, those are indeed correct.

Signature · 3 lines
Bill Davidsen <[email protected]>
 "Woe unto the statesman who makes war without a reason that will still
 be valid when the war is over..." Otto von Bismark