linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: James Bottomley <jbottomley@parallels.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	Ewan Milne <emilne@redhat.com>,
	Ren Mingxin <renmx@cn.fujitsu.com>, Joern Engel <joern@logfs.org>,
	James Smart <james.smart@emulex.com>,
	Bart Van Assche <bvanassche@acm.org>,
	Roland Dreier <roland@purestorage.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH 1/3] scsi: Fix erratic device offline during EH
Date: Wed, 23 Oct 2013 11:27:28 +0200	[thread overview]
Message-ID: <52679680.7070209@suse.de> (raw)
In-Reply-To: <1381840900.3752.19.camel@dabdike.lan>

On 10/16/2013 09:22 PM, James Bottomley wrote:
> On Mon, 2013-09-02 at 13:58 +0200, Hannes Reinecke wrote:
>> Commit 18a4d0a22ed6c54b67af7718c305cd010f09ddf8
>> (Handle disk devices which can not process medium access commands)
>> was introduced to offline any device which cannot process medium
>> access commands.
>> However, commit 3eef6257de48ff84a5d98ca533685df8a3beaeb8
>> (Reduce error recovery time by reducing use of TURs) reduced
>> the number of TURs by sending it only on the first failing
>> command, which might or might not be a medium access command.
>> So in combination this results in an erratic device offlining
>> during EH; if the command where the TUR was sent upon happens
>> to be a medium access command the device will be set offline,
>> if not everything proceeds as normal.
>>
>> So instead of checking the EH command in the ->eh_action
>> callback we should rather call ->eh_action when we're
>> about to finish the command _and_ have sent a TUR previously.
>> This should then set the device offline as advertised.
>>
>> Cc: Martin K. Petersen <martin.petersen@oracle.com>
>> Cc: Ewan Milne <emilne@redhat.com>
>> Signed-off-by: Hannes Reinecke <hare@suse.de>
>> ---
>>   drivers/scsi/scsi_error.c | 28 +++++++++++++++++++---------
>>   1 file changed, 19 insertions(+), 9 deletions(-)
>>
>> diff --git a/drivers/scsi/scsi_error.c b/drivers/scsi/scsi_error.c
>> index abf0916..c88cb7e 100644
>> --- a/drivers/scsi/scsi_error.c
>> +++ b/drivers/scsi/scsi_error.c
>> @@ -941,12 +941,6 @@ retry:
>>
>>   	scsi_eh_restore_cmnd(scmd, &ses);
>>
>> -	if (scmd->request->cmd_type != REQ_TYPE_BLOCK_PC) {
>> -		struct scsi_driver *sdrv = scsi_cmd_to_driver(scmd);
>> -		if (sdrv->eh_action)
>> -			rtn = sdrv->eh_action(scmd, cmnd, cmnd_size, rtn);
>> -	}
>> -
>>   	return rtn;
>>   }
>>
>> @@ -964,6 +958,18 @@ static int scsi_request_sense(struct scsi_cmnd *scmd)
>>   	return scsi_send_eh_cmnd(scmd, NULL, 0, scmd->device->eh_timeout, ~0);
>>   }
>>
>> +static int scsi_eh_action(struct scsi_cmnd *scmd, int rtn)
>> +{
>> +	static unsigned char tur_command[6] = {TEST_UNIT_READY, 0, 0, 0, 0, 0};
>> +
>> +	if (scmd->request->cmd_type != REQ_TYPE_BLOCK_PC) {
>> +		struct scsi_driver *sdrv = scsi_cmd_to_driver(scmd);
>> +		if (sdrv->eh_action)
>> +			rtn = sdrv->eh_action(scmd, tur_command, 6, rtn);
>
> This is all a bit pointless.  You've altered eh_action so it's always
> input an eh TUR command, so just eliminate the check of the eh command
> and assume it's a TUR in the implementation (i.e. fix up sd.c)
>
> Once that's done, I think the patch looks like the one below, is that
> OK?
>
Yes, the patch looks okay. No objections from my side.

Acked-by: Hannes Reinecke <hare@suse.de>

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (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

  parent reply	other threads:[~2013-10-23  7:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-02 11:58 [PATCHv6 0/3] New EH command timeout handler Hannes Reinecke
2013-09-02 11:58 ` [PATCH 1/3] scsi: Fix erratic device offline during EH Hannes Reinecke
2013-09-11 14:36   ` Jeremy Linton
2013-10-16 19:22   ` James Bottomley
2013-10-23  8:58     ` Martin K. Petersen
2013-10-23  9:27     ` Hannes Reinecke [this message]
2013-09-02 11:58 ` [PATCH 2/3] scsi: improved eh timeout handler Hannes Reinecke
2013-09-11  9:16   ` Ren Mingxin
2013-09-12 20:49     ` Hannes Reinecke
2013-09-20  7:59   ` Ren Mingxin
2013-10-02 16:24     ` Hannes Reinecke
2013-10-09  7:43       ` [PATCH] scsi: Set the minimum valid value of 'eh_deadline' as 0 Ren Mingxin
2013-10-09  9:38         ` Hannes Reinecke
2013-10-09 12:28         ` Ewan Milne
2013-10-10  8:46           ` Ren Mingxin
2013-09-02 11:58 ` [PATCH 3/3] scsi_error: Update documentation Hannes Reinecke
2013-10-02  7:25 ` [PATCHv6 0/3] New EH command timeout handler Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2013-10-31 13:02 [PATCHv8 " Hannes Reinecke
2013-10-31 13:02 ` [PATCH 1/3] scsi: Fix erratic device offline during EH Hannes Reinecke

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=52679680.7070209@suse.de \
    --to=hare@suse.de \
    --cc=bvanassche@acm.org \
    --cc=emilne@redhat.com \
    --cc=james.smart@emulex.com \
    --cc=jbottomley@parallels.com \
    --cc=joern@logfs.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=renmx@cn.fujitsu.com \
    --cc=roland@purestorage.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;
as well as URLs for NNTP newsgroup(s).