| 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: <1191350862.3530.114.camel@localhost.localdomain> Date: Tue, 02 Oct 2007 13:47:42 -0500 From: James Bottomley <James.Bottomley@...elEye.com> To: Jeff Garzik <jeff@...zik.org> Cc: Andrew Morton <akpm@...ux-foundation.org>, Linus Torvalds <torvalds@...ux-foundation.org>, linux-scsi@...r.kernel.org, LKML <linux-kernel@...r.kernel.org> Subject: Re: [git patch] SCSI aic94xx fix On Tue, 2007-10-02 at 13:21 -0400, Jeff Garzik wrote: > The SCSI maintainer wants to wait until 2.6.25 for this obvious data That's 2.6.24 ... and that's not what I said. I said I wanted to take it via scsi-misc into 2.6.24 and then take it via the stable tree for 2.6.23.x > corruption fix. > > I vehemently disagree. Sure, I'll state my case: This is a bug, but it has no affected users, nor will it because the aic94xx doesn't work on non-x86 architectures by reason of other longstanding bugs (and TODEVICE/FROMDEVICE only matters to architecures which use dma_map_sg to program the IOMMU). Given that we're at -rc9 and counting every patch towards stabilisation, I see no benefit to adding this to the tree because the benefit to users is zero and the detriment from code churn at this stage is potentially non-zero. My recommendation is still to follow what I propose: take it via scsi-misc to 2.6.24-rc1 and then back to 2.5.23.x James - 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