On Sat, Feb 02, 2008 at 03:56:30PM -0500, Mike Snitzer wrote: > On Feb 2, 2008 3:24 PM, Greg KH <greg@xxxxxxxxx> wrote: > > On Fri, Feb 01, 2008 at 07:43:54PM -0500, Mike Snitzer wrote: > > > Hi Greg, > > > > > > Given your recent call for review of the next 2.6.22-stable I'd > > > appreciate it if you and the rest of the stable team would strongly > > > consider this SCSI IO error propagation fix for inclusion in 2.6.22.17 > > > (as well as the other stable trees). > > > > Is the patch in Linus's tree already? > > > > If so, what git commit id? That's a requirement to go into the stable > > tree... > > > > If not, we need to wait until it is. > > Fair enough. Thanks for the clarification. > > That likely leaves us with having James add it to his git tree for > Linus (provided he agrees with the change). Which he and Luben seemed > to agree was the reasonable thin layer of protection that would be > allowed for such out of spec SCSI devices. > > James, how would you like to proceed? The patch fixes the good_bytes > != 0 on HARDWARE_ERROR issue I have been chasing with Mark Salyzyn. After it goes in, can someone notify stable@xxxxxxxxxx that it went in, the git id, and that it should be applied to all older kernel trees? thanks, greg "drowning in -stable patches" k-h - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
