All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <michaelc@cs.wisc.edu>
To: Hannes Reinecke <hare@suse.de>
Cc: James Bottomley <James.Bottomley@suse.de>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] Check return value of fc_block_scsi_eh()
Date: Wed, 13 Oct 2010 15:37:57 -0500	[thread overview]
Message-ID: <4CB618A5.8030108@cs.wisc.edu> (raw)
In-Reply-To: <20101013114228.96669354D8@ochil.suse.de>

On 10/13/2010 06:42 AM, Hannes Reinecke wrote:
>
> fc_block_scsi_eh() might return with status FAST_IO_FAIL
> indicating I/O has been terminated due to fast_io_fail timeout.
> In this case the rport is still blocked, so any error recovery
> will be failing on this port.
> Hence each driver needs to check if the return value from
> fc_block_scsi_eh() is something other than SUCCESS, in which
> case it should just return with that status.
> And we need to update the error handler to deal with a
> status of FAST_IO_FAIL, too.
> And fc_block_scsi_eh() should return SUCCESS on success,
> not 0. Otherwise the calling routine will become confused
> when reusing that value.
>

Is this patch supposed to fix the problem I described or is there more 
patches to follow or do you think I am being too paranoid? It seems the 
patch alone is going to make the problem worse in the drivers you are 
speeding up failure in. In the drivers now checking fc_block_scsi_eh and 
returning when fast io fail is returned then the scsi eh 
scsi_eh_flush_done_q's scsi_finish_command/scsi_queue_insert processing 
is going to get done faster and more likely to conflict with the 
termiante_rport_io callback processing, right?

  parent reply	other threads:[~2010-10-13 20:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-13 11:42 [PATCH] Check return value of fc_block_scsi_eh() Hannes Reinecke
2010-10-13 13:30 ` Christof Schmitt
2010-10-13 20:37 ` Mike Christie [this message]
2010-10-14  6:45   ` Hannes Reinecke
2010-10-14 19:02     ` Mike Christie
2010-10-15  8:39       ` 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=4CB618A5.8030108@cs.wisc.edu \
    --to=michaelc@cs.wisc.edu \
    --cc=James.Bottomley@suse.de \
    --cc=hare@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.