linux-kernel - Re: 2.4.x libata resync

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 16 Sep 2006 15:27:12 +0900
From:	Tejun Heo <htejun@...il.com>
To:	Willy Tarreau <w@....eu>
CC:	Tom Mortensen <tmmlkml@...il.com>, linux-kernel@...r.kernel.org,
	jeff@...zik.org
Subject: Re: 2.4.x libata resync

Hello,

Willy Tarreau 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.

I don't think it's gonna happen.  Later libata changes depend on a 
number of SCSI updates, which in turn are deeply dependent upon new 
driver model used in 2.6.  So, apart from bug fixes, there won't be 2.4 
resync.

-- 
tejun
-
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/