Linux 2.6.25.10
Quoted 3 lines
Again, if the above information is somehow insufficient as to what exactly is fixed in the -stable releases, and anyone has questions about how these release announcements are created, please let me know.
Well, for example:
I have only machines with 32 bit CPUS, none of them is hot-pluggable and none has an i915 graphics chip. All my local users are "trusted", nor am I running any multi-threaded Java applications on SMP systems. (I also have no idea what ICM pages are, but they sound jolly impressive!)
And what is "native_read_tscp" all about?
So why am I being "STRONGLY encouraged to upgrade to this release"? (Your emphasis.) Is it because otherwise you're going to sneak up and burn my house down?
Cheers,
Chris
__________________________________________________________
Not happy with your email address?.
Get the one you really want - millions of new email addresses available now at Yahoo! http://uk.docs.yahoo.com/ymail/new.html
Quoted 7 lines · Chris Rankin
Quoted 3 lines
Again, if the above information is somehow insufficient as to what exactly is fixed in the -stable releases, and anyone has questions about how these release announcements are created, please let me know.
Well, for example:
I have only machines with 32 bit CPUS, none of them is hot-pluggable
All cpus these days can be "virtually" hotplugged :)
Quoted 6 lines
and none has an i915 graphics chip. All my local users are "trusted", nor am I running any multi-threaded Java applications on SMP systems. (I also have no idea what ICM pages are, but they sound jolly impressive!)
And what is "
native_read_tscp" all about?
Ask the developer who did that.
Quoted 3 lines
So why am I being "STRONGLY encouraged to upgrade to this release"? (Your emphasis.) Is it because otherwise you're going to sneak up and burn my house down?
Fixing an ABI breakage that you could hit might be a good thing for you to have, as well as the other general fixes.
If you can read the changelog and see that you feel you can skip this release, fine. Otherwise, please upgrade.
thanks,
greg k-h
On 4 Jul 2008, Chris Rankin stated:
Quoted 5 lines
I have only machines with 32 bit CPUS, none of them is hot-pluggable and none has an i915 graphics chip. All my local users are "trusted", nor am I running any multi-threaded Java applications on SMP systems. (I also have no idea what ICM pages are, but they sound jolly impressive!)
A good clue here is to look at the subdirectories that were touched. The ICM stuff says in the commit log
IB/mthca: Clear ICM pages before handing to FW
and touches only files under drivers/infiniband/hw/mthca.
So if you don't use the InfiniBand driver, you're almost certainly safe (and from what I understand of InfiniBand, if you're not running a huge corporate SAN or something you're highly unlikely to be using it).
Quoted 3 lines
And what is "
native_read_tscp" all about?From the name I would have assumed something about networking with some
strangely-named protocol, but from the file being touched, include/asm-x86/msr.h, it's something to do with x86 model-specific registers. One function in that header calls it: rdtscp()'. A grep -R for rdtscp' under arch/x86 indicates that there is a word in /proc/cpuinfo devoted to indicating whether your CPU has this feature. If it doesn't, the bug doesn't affect you.
Quoted 1 line
From the other hit, rdtscp()'s one call site, it seems to be some way to
get the current CPU fast on SMP x86-64 boxes. So perhaps you should upgrade if you have one of those.
Generally a bit of grepping and matching on pathnames like this is enough to comprehensively rule most changes in or out as things that affect you, and of course if there are changes to mm code or something like that it's generally a good idea to upgrade anyway, because you can't very well avoid using said code.
Quoted 2 lines
(Your emphasis.) Is it because otherwise you're going to sneak up and burn my house down?
Greg would never do a thing like that without forewarning.
Quoted 9 lines · Chris Rankin
Quoted 3 lines
Again, if the above information is somehow insufficient as to what exactly is fixed in the -stable releases, and anyone has questions about how these release announcements are created, please let me know.
Well, for example:
I have only machines with 32 bit CPUS, none of them is hot-pluggable and none has an i915 graphics chip. All my local users are "trusted", nor am I running any multi-threaded Java applications on SMP systems. (I also have no idea what ICM pages are, but they sound jolly impressive!)
And what is "
native_read_tscp" all about?
To some degree I can understand that you are not sure of whether you are affected or not. On the other hand you should probably be, when running your own kernels on a productive system. After all there seems to be a general agreement that distribution vendors take care of the stabilization and bug fixing of their particular kernels. As far as I am concerned, I'm grateful that there are these stable releases at all and I very much consider it additional work for everyone in the release team. To that end it should be your task to check whether the update affects you or not.
After all the releases are publicly announced on probably the busiest mailing list on earth. That offers anyone the chance to add additional information to the releases (there has been a discussion recently about security implications that weren't mentioned in the announcement. Just replying to the announcement will add the needed information, and as the discussion showed, people actually do add information).
To sum all the above up: IMHO the announcements are great, the work of the stable team is great and I wouldn't really want to push more work on the people that voluntarily spend their time on this branch by explaining every detail of every patch.
Just my 2 cents.
Best regards,
Stefan