On 14-10-24 04:51 PM, Christoph Hellwig wrote:
On Tue, Oct 14, 2014 at 12:42:26PM -0400, Douglas Gilbert wrote:
I don't mind if you change it. However I plan to release
sg3_utils-1.40 in the next 2 or 3 weeks, so that would
be the earliest a revised sg_reset would be available for
distros. Impro
On Tue, Oct 14, 2014 at 12:42:26PM -0400, Douglas Gilbert wrote:
> I don't mind if you change it. However I plan to release
> sg3_utils-1.40 in the next 2 or 3 weeks, so that would
> be the earliest a revised sg_reset would be available for
> distros. Improving error reports is something I always
>
> -Original Message-
> From: Christoph Hellwig [mailto:h...@infradead.org]
> Sent: Wednesday, 15 October, 2014 8:26 AM
...
> On Tue, Oct 14, 2014 at 12:42:26PM -0400, Douglas Gilbert wrote:
> > I don't mind if you change it. However I plan to release
> > sg3_utils-1.40 in the next 2 or 3
On Tue, Oct 14, 2014 at 12:42:26PM -0400, Douglas Gilbert wrote:
> I don't mind if you change it. However I plan to release
> sg3_utils-1.40 in the next 2 or 3 weeks, so that would
> be the earliest a revised sg_reset would be available for
> distros. Improving error reports is something I always
>
On 14-10-14 07:13 AM, Christoph Hellwig wrote:
On Sat, Oct 11, 2014 at 10:06:47PM +, Elliott, Robert (Server Storage)
wrote:
Thanks. That's a bit better, but sg_reset can now run into
"No such device" errors.
That's the -ENODEV we return if another reset is in progress. Given
that I sus
On Sat, Oct 11, 2014 at 10:06:47PM +, Elliott, Robert (Server Storage)
wrote:
> Thanks. That's a bit better, but sg_reset can now run into
> "No such device" errors.
That's the -ENODEV we return if another reset is in progress. Given
that I suspect sg_reset is the prime if not only user of
On Mon, Oct 13, 2014 at 11:15:19AM +0200, Bart Van Assche wrote:
> At least to me patches 1/4..3/4 look like nice cleanup patches. Regarding
> patch 4/4: I'm not sure yet what's the best way for addressing potentially
> concurrent SG_SCSI_RESET ioctl calls. As far as I know many SCSI LLDs have
> be
On 10/11/14 18:11, Christoph Hellwig wrote:
Hi Robert,
can you take a look at the patches at:
http://git.infradead.org/users/hch/scsi.git/shortlog/refs/heads/scsi-ioctl
and confirm if they fix your issue?
Hello Christoph,
At least to me patches 1/4..3/4 look like nice cleanup patches.
Rega
> > From: Christoph Hellwig [mailto:h...@infradead.org]
> > Sent: Saturday, 11 October, 2014 11:11 AM
...
> >
> > Hi Robert,
> >
> > can you take a look at the patches at:
> >
> > http://git.infradead.org/users/hch/scsi.git/shortlog/refs/heads/scsi-ioctl
> >
> > and confirm if they fix your issue
er.kernel.org; Don Brace (PMC); Scales,
> Webb
> Subject: Re: Concurrent SG_SCSI_RESET ioctls
>
> Hi Robert,
>
> can you take a look at the patches at:
>
> http://git.infradead.org/users/hch/scsi.git/shortlog/refs/heads/scsi-ioctl
>
> and confirm if they fix your issue?
Hi Robert,
can you take a look at the patches at:
http://git.infradead.org/users/hch/scsi.git/shortlog/refs/heads/scsi-ioctl
and confirm if they fix your issue?
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majord...@vger.kernel.org
More ma
On Fri, Oct 10, 2014 at 11:32:26PM +, Elliott, Robert (Server Storage)
wrote:
> Problem
> ===
> If you run sg_reset --device concurrently to multiple
> devices on the same host, then some of them will run
> into tmf_in_progress and have scsi_nonblockable_ioctl
> return -ENODEV. This cause
12 matches
Mail list logo
