public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: wenxiong@linux.vnet.ibm.com,
	James.Bottomley@HansenPartnership.com,
	linux-scsi@vger.kernel.org, brking@linux.vnet.ibm.com, "Elliott,
	Robert (Server Storage)" <elliott@hp.com>
Subject: Re: [V2 PATCH 2/2] scsi: TUR path is down after adapter gets reset with multipath
Date: Wed, 05 Nov 2014 09:56:24 +0100	[thread overview]
Message-ID: <5459E638.6010707@suse.de> (raw)
In-Reply-To: <20141104150152.GA17309@infradead.org>

On 11/04/2014 04:01 PM, Christoph Hellwig wrote:
> On Tue, Nov 04, 2014 at 08:21:13AM +0100, Hannes Reinecke wrote:
>> Why did you use a wrapper for an already existing function?
>> Please fold the logic into alua_check_sense().
> 
> That's what the first version did.  See the response from Rob to it
> on why it's done this way.

Hmm. I see. But I still thing it should be wrapped into
alua_check_sense().
The main objection from Rob was that a sense code of 02/04/02 should
cause a START STOP UNIT to be sent, but the latter is might be
invalid for certain ALUA states.
Thing is, we're only sending START STOP UNIT as part of the main
SCSI EH routine, so that would work in either way.

And looking a scsi_dh_alua we're only checking a return value of
ADD_TO_MLQUEUE; any other value is treated as an I/O error.
So it doesn't really matter if alua_check_sense would return
FAILED here; it still would be folded into the final return value of
SCSI_DH_IO.

So I don't think we need to have a wrapper around alua_check_sense()
but can rather merge them both.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 21284 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2014-11-05  8:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-03 21:18 [V2 PATCH 0/2] TUR path is down after adapter gets reset in multipath configuration wenxiong
2014-11-03 21:18 ` [V2 PATCH 1/2] scsi: call device handler for failed TUR command wenxiong
2014-11-03 21:18 ` [V2 PATCH 2/2] scsi: TUR path is down after adapter gets reset with multipath wenxiong
2014-11-04  7:21   ` Hannes Reinecke
2014-11-04 15:01     ` Christoph Hellwig
2014-11-05  8:56       ` Hannes Reinecke [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-11-03 21:28 [ V2 PATCH 0/2] TUR path is down after adapter gets reset in multipath configuration wenxiong
2014-11-03 21:28 ` [ V2 PATCH 2/2] scsi: TUR path is down after adapter gets reset with multipath wenxiong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5459E638.6010707@suse.de \
    --to=hare@suse.de \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=brking@linux.vnet.ibm.com \
    --cc=elliott@hp.com \
    --cc=hch@infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=wenxiong@linux.vnet.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox