From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: "James E . J . Bottomley" <jejb@linux.ibm.com>,
Steffen Maier <maier@linux.ibm.com>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
linux-scsi@vger.kernel.org, Vasily Gorbik <gor@linux.ibm.com>,
linux-s390@vger.kernel.org, Heiko Carstens <hca@linux.ibm.com>,
Benjamin Block <bblock@linux.ibm.com>
Subject: Re: [PATCH] zfcp: fix failed recovery on gone remote port with non-NPIV FCP devices
Date: Tue, 25 Jan 2022 00:40:42 -0500 [thread overview]
Message-ID: <164308671271.32373.2878476881217752247.b4-ty@oracle.com> (raw)
In-Reply-To: <20220118165803.3667947-1-maier@linux.ibm.com>
On Tue, 18 Jan 2022 17:58:03 +0100, Steffen Maier wrote:
> Suppose we have an environment with a number of non-NPIV FCP devices
> (virtual HBAs / FCP devices / zfcp "adapter"s) sharing the same physical
> FCP channel (HBA port) and its I_T nexus. Plus a number of storage target
> ports zoned to such shared channel. Now one target port logs out of the
> fabric causing an RSCN. Zfcp reacts with an ADISC ELS and subsequent port
> recovery depending on the ADISC result. This happens on all such FCP
> devices (in different Linux images) concurrently as they all receive a copy
> of this RSCN. In the following we look at one of those FCP devices.
>
> [...]
Applied to 5.17/scsi-fixes, thanks!
[1/1] zfcp: fix failed recovery on gone remote port with non-NPIV FCP devices
https://git.kernel.org/mkp/scsi/c/8c9db6679be4
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2022-01-25 5:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 16:58 [PATCH] zfcp: fix failed recovery on gone remote port with non-NPIV FCP devices Steffen Maier
2022-01-19 3:43 ` Martin K. Petersen
2022-01-25 5:40 ` Martin K. Petersen [this message]
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=164308671271.32373.2878476881217752247.b4-ty@oracle.com \
--to=martin.petersen@oracle.com \
--cc=bblock@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=jejb@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=maier@linux.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 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.