[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110114011538.GB21818@redhat.com>
Date: Thu, 13 Jan 2011 20:15:39 -0500
From: Mike Snitzer <snitzer@...hat.com>
To: Hannes Reinecke <hare@...e.de>, k-ueda@...jp.nec.com,
michaelc@...wisc.edu, tytso@....edu, sshtylyov@...sta.com,
linux-scsi@...r.kernel.org, jaxboe@...ionio.com, jack@...e.cz,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
swhiteho@...hat.com, linux-raid@...r.kernel.org,
linux-ide@...r.kernel.org, dm-devel@...hat.com,
James.Bottomley@...e.de, konishi.ryusuke@....ntt.co.jp,
j-nomura@...jp.nec.com, vst@...b.net, rwheeler@...hat.com,
hch@....de, chris.mason@...cle.com, tj@...nel.org
Subject: Re: [RFC PATCH 0/3] differentiate between I/O errors
On Fri, Dec 10 2010 at 6:40pm -0500,
Malahal Naineni <malahal@...ibm.com> wrote:
> Mike Snitzer [snitzer@...hat.com] wrote:
> > Refreshed Hannes' initial "scsi: Detailed I/O errors" patch against
> > v2.6.37-rc5. v2 introduces __scsi_error_from_host_byte to avoid
> > the duplicate switch statement. Also a few whitespace and comment
> > changes.
> >
> > Split DM mpath change out to separate v2 patch; failed discard is now
> > retryable in the face of a non-target IO error.
> >
> > Added improved block layer's I/O error message (based on the finer
> > grained I/O error returns afforded by SCSI).
> >
> > Comments/suggestions are welcome.
>
> I did test the Hannes original patch with the latest Linus' git tree! I
> used scsi_debug to simulate path failures as well as 'Media' failures
> and it did work as expected. I will test your patches soon.
Hi Malahal,
I was wondering if you had any feedback (testing or otherwise) for these
patches:
https://patchwork.kernel.org/patch/384612/
https://patchwork.kernel.org/patch/384602/
https://patchwork.kernel.org/patch/390882/
We haven't heard from Hannes in a bit but I was hoping we could at least
understand that the few changes I made are agreeable and working as
expected.
Thanks,
Mike
--
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