From: Himanshu Madhani <hmadhani@marvell.com>
To: Martin Wilck <Martin.Wilck@suse.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Quinn Tran <qutran@marvell.com>
Cc: Bart Van Assche <Bart.VanAssche@sandisk.com>,
James Bottomley <jejb@linux.vnet.ibm.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
Hannes Reinecke <hare@suse.de>
Subject: Re: [EXT] [PATCH 0/2] scsi: qla2xxx: Fix rport removal after unzoning
Date: Fri, 22 Nov 2019 22:53:54 +0000 [thread overview]
Message-ID: <5A4623F6-6B62-4482-A62C-4D4964B3ECD7@marvell.com> (raw)
On 11/22/19, 4:19 PM, "Martin Wilck" <Martin.Wilck@suse.com> wrote:
External Email
----------------------------------------------------------------------
From: Martin Wilck <mwilck@suse.com>
These two patches fix similar problems that occur if an initiator port
belongs only to a single zone, and this zone is removed in the fabric.
The driver doesn't notice the ports being removed, and the device nodes
persist in the host, yielding IO errors when accessed.
These are pretty old regressions, introduced before 4.16, qla2xxx
10.00.00.04-k. The "Fixes:" tags I provide are only approximate, because
the driver changed the RSCN handling in several steps.
The first patch affects only "legacy" FC adapters using synchonous
fabric scan. The second one is for newer adapters using async scanning,
and applies if the GPN_FT/GNN_FT commands sent by the adapter fail.
Martin Wilck (2):
scsi: qla2xxx: fix rports not being mark as lost in sync fabric scan
scsi: qla2xxx: unregister ports after GPN_FT failure
drivers/scsi/qla2xxx/qla_gs.c | 16 ++++++++++++++--
drivers/scsi/qla2xxx/qla_init.c | 6 +++---
2 files changed, 17 insertions(+), 5 deletions(-)
--
2.24.0
Looks good.
Acked-by: Himanshu Madhani <hmadhani@marvell.com>
reply other threads:[~2019-11-22 22:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5A4623F6-6B62-4482-A62C-4D4964B3ECD7@marvell.com \
--to=hmadhani@marvell.com \
--cc=Bart.VanAssche@sandisk.com \
--cc=Martin.Wilck@suse.com \
--cc=hare@suse.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=qutran@marvell.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.