From: Hannes Reinecke <hare@suse.de>
To: james.smart@emulex.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 06/21] lpfc: Fix host reset escalation killing all IOs.
Date: Fri, 10 Apr 2015 08:10:38 +0200 [thread overview]
Message-ID: <5527695E.4050109@suse.de> (raw)
In-Reply-To: <1428095489.6933.34.camel@myfc17>
On 04/03/2015 11:11 PM, James Smart wrote:
> Fix host reset escalation killing all IOs.
>
> SLI-3 adapters will use a new host template. The template differs
> from SLI-4 adapters in that it does not have an eh_host_reset_handler.
>
> Lpfc has traditionally never had a host_reset. The host reset
> handler was added when we ran into a stuck hardware condition on a
> SLI-4 adapter. The host_reset will reset and reinit the pci function,
> clearing the hardware condition.
>
> Unfortunately, the host reset handler uses attach/detach code paths,
> which makes scsi_add_host() and scsi_remove_host() calls. Meaning, a
> host_reset will completely remove the scsi_host from the system. As a
> new call to scsi_add_host() is made, the shost# changes, which results
> in completely new scsi_devices and device names. All the older scsi
> devices on the old shost# are now orphaned and unrecoverable.
>
> We realize we need to re-implement the host_reset_handler so the scsi_host
> stays registered across the host_reset, but that will be a rather
> lengthy effort. In the short term, we had an immediate need to restore
> the SLI-3 devices to their working behavior, with the easiest path being
> to remove their host_reset handler.
>
> Signed-off-by: Dick Kennedy <dick.kennedy@emulex.com>
> Signed-off-by: James Smart <james.smart@emulex.com>
> ---
Of course, this will disable the eh_deadline mechanism, which relies
on the host_reset to be present.
Of which you are perfectly aware :-)
So, grudgingly:
Reviewed-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
next prev parent reply other threads:[~2015-04-10 6:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-03 21:11 [PATCH 06/21] lpfc: Fix host reset escalation killing all IOs James Smart
2015-04-10 6:10 ` Hannes Reinecke [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-02-05 19:23 James Smart
2015-03-07 16:56 ` James Bottomley
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=5527695E.4050109@suse.de \
--to=hare@suse.de \
--cc=james.smart@emulex.com \
--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 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).