lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <20071209220132.53268368@the-village.bc.nu> Date: Sun, 9 Dec 2007 22:01:32 +0000 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: Tejun Heo <htejun@...il.com>, Andrew Morton <akpm@...ux-foundation.org>, "Rafael J. Wysocki" <rjw@...k.pl>, LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu> Subject: Re: 2.6.24-rc4-git5: Reported regressions from 2.6.23 > Btw, Alan, that "math" is total and utter BULLSH*T, and you should know > that. The one off regression is probably not one off, but this is IDE so actually its quite probable its a single broken firmware. The alternative is that you cripple just about every user of various other standards compliant devices and controllers whose hardware we finally fixed. Finally you need to remember that the 'regression' is caused by the fact we now do the _right_ thing both in terms of 'old IDE' and specs. Believe it or not I did actually think in quite some detail about this case, and the relative probabilities, and go back and re-review the old IDE code (whose behaviour we now follow) and the spec. I spend a measurable amount of my time reviewing code and weighing risks, regressions and progress for an enterprise Linux vendor, so its something I do every day of the week. To blindly argue regressions are critical is sometimes (as in this case) to argue that "this freeway is no longer compatible with a horse and cart" means the freeway should be turned back into a dirt road. The horse and cart happened to work by chance because the road was quiet that day. We clearly need to add a horse & cart lane in the long term, but for 2.6.24 it may well be the right thing to do just to blacklist that specific drive back to old behaviour until we can tidy it more nicely. Alan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists