From: Christof Schmitt <christof.schmitt@de.ibm.com>
To: James Bottomley <James.Bottomley@suse.de>
Cc: linux-scsi@vger.kernel.org, Mike Christie <michaelc@cs.wisc.edu>,
Hannes Reinecke <hare@suse.de>
Subject: [patch 0/2] [PATCH/RESEND] Stop scsi eh when fast_io_fail_tmo fires
Date: Thu, 01 Apr 2010 13:48:48 +0200 [thread overview]
Message-ID: <20100401114848.628357000@de.ibm.com> (raw)
James,
these are the same two patches i submitted to linux-scsi before. The
initial submission went only to linux-scsi, so here it is again with
the appropriate cc list. The patches solve the problem of the scsi eh
blocking the host until the dev_loss_tmo fires, allowing the scsi eh
to stop already when the fast_io_fail_tmo fires. Hannes and Mike agree
with this approach.
The patches apply to both, the current scsi-misc and the current
scsi-rc-fixes tree, i am not quite sure which tree would be more
appropriate.
--
Christof
next reply other threads:[~2010-04-01 11:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 11:48 Christof Schmitt [this message]
2010-04-01 11:48 ` [patch 1/2] scsi: Allow FC LLD to fast-fail scsi eh Christof Schmitt
2010-04-01 11:48 ` [patch 2/2] zfcp: Pass return code from fc_block_scsi_eh to " Christof Schmitt
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=20100401114848.628357000@de.ibm.com \
--to=christof.schmitt@de.ibm.com \
--cc=James.Bottomley@suse.de \
--cc=hare@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
/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