SATA support merge in 2.4.27
Hi,
Jeff Garzik sent me a SATA update to be merged in 2.4.x.
A lot of new boxes are shipping with SATA-only disks, and its pretty bad to not have a "stable" series without such industry-standard support.
This is the last feature to be merged on 2.4.x, and only because its quite necessary.
Any oppositions?
Quoted 10 lines · Marcelo Tosatti
Hi,
Jeff Garzik sent me a SATA update to be merged in 2.4.x.
A lot of new boxes are shipping with SATA-only disks, and its pretty bad to not have a "stable" series without such industry-standard support.
This is the last feature to be merged on 2.4.x, and only because its quite necessary.
Any oppositions?
There are alternative ways* to get sata support for some chips but I believe it's the right choice to do the 'full' route so I believe it's the right choice. 2.4 will still be used for quite a while, especially until "everybody" trusts 2.6, same way that happened with 2.2 and 2.4 ..
* siimage.c, add sata8237 entry to via driver, etc...
// Stefan
Quoted 6 lines · Marcelo Tosatti
Hi,
Jeff Garzik sent me a SATA update to be merged in 2.4.x.
A lot of new boxes are shipping with SATA-only disks, and its pretty bad to not have a "stable" series without such industry-standard support.
I also sent you a new driver that is unrelated to libata.
Jeff
Marcelo,
To be RUDELY BLUNT! When in the hell did it matter in the past?
Recall your failure to include ATA133 and SATA 1.0 back in 2.4.16-19.
I actually object to it on the sheer principle of past history.
Regards,
Andre Hedrick
LAD Storage Consulting Group
Quoted 17 lines · Marcelo Tosatti
Hi,
Jeff Garzik sent me a SATA update to be merged in 2.4.x.
A lot of new boxes are shipping with SATA-only disks, and its pretty bad to not have a "stable" series without such industry-standard support.
This is the last feature to be merged on 2.4.x, and only because its quite necessary.
Any oppositions?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Marcelo,
You are suggesting that 2.6 is not stable ? How could that be ? Should it not be backported to 2.2 and why not 2.0 ?
What about the rest of the feature sets ?
Necessary? But their is the new and improved called 2.6. It is time for the old and lousy to quietly wimper off and die.
Regards,
Andre Hedrick
LAD Storage Consulting Group
Quoted 40 lines · Andre Hedrick
Marcelo,
To be RUDELY BLUNT! When in the hell did it matter in the past?
Recall your failure to include ATA133 and SATA 1.0 back in 2.4.16-19.
I actually object to it on the sheer principle of past history.
Regards,
Andre Hedrick
LAD Storage Consulting GroupQuoted 10 lines · Marcelo Tosatti
Hi,
Jeff Garzik sent me a SATA update to be merged in 2.4.x.
A lot of new boxes are shipping with SATA-only disks, and its pretty bad to not have a "stable" series without such industry-standard support.
This is the last feature to be merged on 2.4.x, and only because its quite necessary.
Quoted 7 lines
Any oppositions?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Quote from Andre Hedrick <[email protected]>:
Quoted 1 line
You are suggesting that 2.6 is not stable ? How could that be ?
It hasn't exactly been audited for security issues yet.
John.
Quoted 4 lines · John Bradford
Quote from Andre Hedrick <[email protected]>:
Quoted 1 line
You are suggesting that 2.6 is not stable ? How could that be ?
It hasn't exactly been audited for security issues yet.
neither has the biggest part of the 2.4 codebase.
Quote from Arjan van de Ven <[email protected]>:
Quoted 5 lines
--=-De0mPL9BnMYZGB8TurTV
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
Quoted 7 lines
Quoted 4 lines · John Bradford
Quote from Andre Hedrick <[email protected]>:
Quoted 1 line
You are suggesting that 2.6 is not stable ? How could that be ?
=20
It hasn't exactly been audited for security issues yet.neither has the biggest part of the 2.4 codebase.
A valid point, but last time I checked, there were known exploits that had been fixed in 2.4 but not in 2.6.
John.
Quoted 8 lines · John Bradford
Quote from Arjan van de Ven <[email protected]>:
Quoted 7 lines
--=-De0mPL9BnMYZGB8TurTV
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printableQuoted 1 line · John Bradford
Quote from Andre Hedrick <[email protected]>:
Quoted 8 lines
Quoted 5 lines
Quoted 3 lines
Quoted 1 line
You are suggesting that 2.6 is not stable ? How could that be ?
=20
It hasn't exactly been audited for security issues yet.neither has the biggest part of the 2.4 codebase.
A valid point, but last time I checked, there were known exploits that had been fixed in 2.4 but not in 2.6.
maybe you should check again and report what you find because I for sure can't think of any.
Quote from Arjan van de Ven <[email protected]>:
Quoted 18 lines
--g7w8+K/95kPelPD2
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inlineQuoted 12 lines · John Bradford
Quote from Arjan van de Ven <[email protected]>:
Quoted 11 lines
--=-De0mPL9BnMYZGB8TurTV
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printableQuoted 4 lines · John Bradford
Quote from Andre Hedrick <[email protected]>:
Quoted 1 line
You are suggesting that 2.6 is not stable ? How could that be ?
=20
It hasn't exactly been audited for security issues yet.
Quoted 7 lines
Quoted 4 lines
Quoted 1 line
neither has the biggest part of the 2.4 codebase.
A valid point, but last time I checked, there were known exploits that had been fixed in 2.4 but not in 2.6.
maybe you should check again and report what you find because I for sure can't think of any.
I honestly don't have the time to go through the archives at the moment, and having been busy, I could well have missed any fixes that have gone in during the last couple of releases, but I am 99% sure that Alan identified a couple of local root exploits around 2.6.0 that had been fixed in 2.4 but never applied to 2.6.
John.
Quoted 2 lines · John Bradford
of local root exploits around 2.6.0 that had been fixed in 2.4 but never applied to 2.6.
we're at 2.6.6-rc1 now, and afaik all those got applied.
On Friday 16 April 2004 14:37, John Bradford wrote:
Hi,
Quoted 10 lines
Quoted 4 lines
Quoted 2 lines
A valid point, but last time I checked, there were known exploits that had been fixed in 2.4 but not in 2.6.
maybe you should check again and report what you find because I for sure can't think of any.
I honestly don't have the time to go through the archives at the moment, and having been busy, I could well have missed any fixes that have gone in during the last couple of releases, but I am 99% sure that Alan identified a couple of local root exploits around 2.6.0 that had been fixed in 2.4 but never applied to 2.6.
well, last time I checked that (some weeks ago), also reading must-fix.txt, all 2.4 security fixes are in 2.6 now too. IMHO we should update must-fix.txt so it does not tell there are 60-70 security vulns not fixed yet.
ciao, Marc
Since we are going over the cliff, lets get there faster!
Has 2.2 or 2.0 ever been audited for security issues, and fixed?
Whee this is fun!
Andre Hedrick
LAD Storage Consulting Group
Quoted 19 lines · John Bradford
Quote from Arjan van de Ven <[email protected]>:
Quoted 5 lines
--=-De0mPL9BnMYZGB8TurTV
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printableQuoted 7 lines
Quoted 4 lines · John Bradford
Quote from Andre Hedrick <[email protected]>:
Quoted 1 line
You are suggesting that 2.6 is not stable ? How could that be ?
=20
It hasn't exactly been audited for security issues yet.neither has the biggest part of the 2.4 codebase.
A valid point, but last time I checked, there were known exploits that had been fixed in 2.4 but not in 2.6.
John.
Quote from Andre Hedrick <[email protected]>:
Quoted 6 lines
Since we are going over the cliff, lets get there faster!
Has 2.2 or 2.0 ever been audited for security issues, and fixed?
Whee this is fun!
I don't really see the relevence of what you're saying.
Maybe I wasn't clear when I said 'audited for security issues' - I meant ensuring that fixes for 2.4 also eventually went in to 2.6. I'm not talking about doing any kind of complete audit of the entire codebase.
For a long time, (since before 2.6.0), there were known local root exploits that had been fixed in 2.4 and not in 2.6. I never saw those fixed, but I don't have the details of them to hand, nor do I have the time to search through years of mailing list archives at the moment. However, I am also not claiming that 2.6 is stable, (yet).
John.
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 4 lines · Marcelo Tosatti
Marcelo,
You are suggesting that 2.6 is not stable ? How could that be ?
It is stable, but some people still use 2.4 for production machines, and will still do for sometime.
Quoted 1 line
Should it not be backported to 2.2 and why not 2.0 ?
The amount of people using 2.2/2.0 and SATA is probably small.
But sure, why dont you start the backport ?
Quoted 1 line
What about the rest of the feature sets ?
This is not like "the rest of the feature sets", this is basic functionality needed to support new systems in the market.
And again, unfortunately not everyone is running v2.6 on their production environment, yet.
Quoted 2 lines
Necessary? But their is the new and improved called 2.6. It is time for the old and lousy to quietly wimper off and die.
Right, the old and lousy should wimper off and die. But this is a special case (a lot of people are applying SATA by hand, look at lkml).
Quoted 3 lines
Marcelo,
You are suggesting that 2.6 is not stable ? How could that be ?
Andre, ressure me, you were drunk ?
A stable kernel is a kernel in which a new release does not induce 20 rejects when applying the same patches as on the previous one, and in which you can confidently upgrade to fix a security issue without worrying that everything else will break under your feet. I'm really happy that 2.4 *WILL* become stable with 2.4.27, and probably will be the first 2.4 kernel ready for far remote deployment. Since about 2.4.23, it has become a lot easier to maintain up-to-date parallel trees in sync with Marcelo's because of less core changes all the time, and I really thank him for this progressive feature freeze. When I'll have a fair insurance that 2.6 does not change so fast, may be I'll start to think about it. But right now, 2.6 only serves me as a boot loader in conjunction with Randy's kexec patch. Sad but true.
Quoted 1 line
Should it not be backported to 2.2 and why not 2.0 ?
I thought you were more aware than that about the number of people still using 2.0 and 2.2. They are "a lot". What does "a lot" mean ? Well, I think that there are more people still running production machines on 2.2 and 2.0 than people who have ever used 1.0 or 1.2. And at these times, we considered that "a lot". I know some people who still install RedHat 6.2 from time to time. Why do they do this ? certainly because a standard 2.2.26 kernel + grsecurity offers them enough stability and security to satisfy their needs and not to have to upgrade every 4 months.
Quoted 2 lines
Necessary? But their is the new and improved called 2.6. It is time for the old and lousy to quietly wimper off and die.
I would better say that it's time for the old and stable to live long and quitely, and for the young baby to slowly discover the desktop world, then the production world before engaging its reputation on mission-critical systems.
Regards,
Willy
Willy,
I do not drink. I have enough trouble keeping friends when I am sobber. Sheesh, I worked for Merkey before and drinking and posting is a bad idea.
Point being, it was not important in the beginning ... so it is not important now. Being consistant is one thing I have always been.
Regards,
Andre Hedrick
LAD Storage Consulting Group
Quoted 46 lines · Willy Tarreau
Quoted 3 lines
Marcelo,
You are suggesting that 2.6 is not stable ? How could that be ?
Andre, ressure me, you were drunk ?
A stable kernel is a kernel in which a new release does not induce 20 rejects when applying the same patches as on the previous one, and in which you can confidently upgrade to fix a security issue without worrying that everything else will break under your feet. I'm really happy that 2.4 *WILL* become stable with 2.4.27, and probably will be the first 2.4 kernel ready for far remote deployment. Since about 2.4.23, it has become a lot easier to maintain up-to-date parallel trees in sync with Marcelo's because of less core changes all the time, and I really thank him for this progressive feature freeze. When I'll have a fair insurance that 2.6 does not change so fast, may be I'll start to think about it. But right now, 2.6 only serves me as a boot loader in conjunction with Randy's kexec patch. Sad but true.
Quoted 1 line
Should it not be backported to 2.2 and why not 2.0 ?
I thought you were more aware than that about the number of people still using 2.0 and 2.2. They are "a lot". What does "a lot" mean ? Well, I think that there are more people still running production machines on 2.2 and 2.0 than people who have ever used 1.0 or 1.2. And at these times, we considered that "a lot". I know some people who still install RedHat 6.2 from time to time. Why do they do this ? certainly because a standard 2.2.26 kernel + grsecurity offers them enough stability and security to satisfy their needs and not to have to upgrade every 4 months.
Quoted 2 lines
Necessary? But their is the new and improved called 2.6. It is time for the old and lousy to quietly wimper off and die.
I would better say that it's time for the old and stable to live long and quitely, and for the young baby to slowly discover the desktop world, then the production world before engaging its reputation on mission-critical systems.
Regards,
Willy-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Quoted 6 lines · Andre Hedrick
Marcelo,
To be RUDELY BLUNT! When in the hell did it matter in the past?
Recall your failure to include ATA133 and SATA 1.0 back in 2.4.16-19.
ATA133 was merged by Alan Cox in 2.4.21. SATA 1.0 was posted by Jeff in the past, but I preferred to hold it for a while (to make sure its more stable).
It now seems Jeff is more confident with it.
Quoted 1 line
I actually object to it on the sheer principle of past history.
This is a special case. I dont see any good arguments to not merge it from you.