| 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
| ||
|
Date: Fri, 15 Sep 2006 23:47:35 -0700 From: "Tom Mortensen" <tmmlkml@...il.com> To: linux-kernel@...r.kernel.org Subject: Re: 2.4.x libata resync Thank you for the info. In studying the code that's what my impression was as well (that it would require a considerable effort). I haven't encountered any problems with SATA in 2.4.33, but I guess what I was concerned about was when/if it might become necessary to migrate to 2.6.x in order to support newer hardware. I guess I'll know when I encounter it :) On 9/15/06, Willy Tarreau <w@....eu> wrote: > On Fri, Sep 15, 2006 at 10:14:07PM -0700, Tom Mortensen wrote: > > To Jeff Garzik & others, > > I was wondering if there are any plans for another resync of the latest > > 2.6.x libata changes back into the 2.4.x kernel? > > When Jeff posted his last version (which got merged), he said that it > would be his last work on this backport. I've been regularly checking > what has changed in 2.6, because often some bugs are fixed, but I see > that the code has considerably evolved since the last resync, and I'm > not even sure that those bugfixes are needed for 2.4. > > A full resync of latest 2.6 would require a considerable effort it seems. > Do you encounter any problems right now ? I get very few feedback from > SATA users in general. > > Regards, > Willy > > - 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