From: Mike Christie <michael.christie@oracle.com>
To: Wenchao Hao <haowenchao@huawei.com>,
Lee Duncan <lduncan@suse.com>, Chris Leech <cleech@redhat.com>,
"James E . J . Bottomley" <jejb@linux.ibm.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
open-iscsi@googlegroups.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: linfeilong@huawei.com
Subject: Re: [PATCH 2/2] iscsi: set session to FREE state after unbind session in remove session
Date: Thu, 14 Apr 2022 10:30:40 -0500 [thread overview]
Message-ID: <a8087705-2cea-f01c-ce67-639e97edc30a@oracle.com> (raw)
In-Reply-To: <20220414014947.4168447-3-haowenchao@huawei.com>
On 4/13/22 8:49 PM, Wenchao Hao wrote:
> __iscsi_unbind_session() set session state to ISCSI_SESSION_UNBOUND, which
> would overwrite the ISCSI_SESSION_FREE state.
>
> Signed-off-by: Wenchao Hao <haowenchao@huawei.com>
> ---
> drivers/scsi/scsi_transport_iscsi.c | 26 ++++++++++++++++----------
> 1 file changed, 16 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/scsi/scsi_transport_iscsi.c b/drivers/scsi/scsi_transport_iscsi.c
> index 97a9fee02efa..d8dd9279cea8 100644
> --- a/drivers/scsi/scsi_transport_iscsi.c
> +++ b/drivers/scsi/scsi_transport_iscsi.c
> @@ -2173,6 +2173,22 @@ void iscsi_remove_session(struct iscsi_cls_session *session)
> if (!cancel_work_sync(&session->block_work))
> cancel_delayed_work_sync(&session->recovery_work);
> cancel_work_sync(&session->unblock_work);
> +
> + scsi_target_unblock(&session->dev, SDEV_TRANSPORT_OFFLINE);
> + /*
> + * qla4xxx can perform it's own scans when it runs in kernel only
> + * mode. Make sure to flush those scans.
> + */
> + flush_work(&session->scan_work);
> +
> + /*
> + * flush running unbind operations
> + * if unbind work did not queued, call __iscsi_unbind_session
> + * directly to perform target remove
We probably don't need the flush_work test because we are going to
normally call __iscsi_unbind_session.
If the unbind work had already run, which is the normal case, then
flush_work returns false and we end up calling __iscsi_unbind_session
like before. That function then checks if the target is really unbound.
So the extra check doesn't normally buy us anything with your patches
because in patch 1 you fixed it so __iscsi_unbind_session doesn't send
the extra event.
> + */
> + if (!flush_work(&session->unbind_work))
> + __iscsi_unbind_session(&session->unbind_work);
> +
> /*
> * If we are blocked let commands flow again. The lld or iscsi
> * layer should set up the queuecommand to fail commands.
> @@ -2183,16 +2199,6 @@ void iscsi_remove_session(struct iscsi_cls_session *session)
> session->state = ISCSI_SESSION_FREE;
> spin_unlock_irqrestore(&session->lock, flags);
>
> - scsi_target_unblock(&session->dev, SDEV_TRANSPORT_OFFLINE);
> - /*
> - * qla4xxx can perform it's own scans when it runs in kernel only
> - * mode. Make sure to flush those scans.
> - */
> - flush_work(&session->scan_work);
> - /* flush running unbind operations */
> - flush_work(&session->unbind_work);
> - __iscsi_unbind_session(&session->unbind_work);
> -
> /* hw iscsi may not have removed all connections from session */
> err = device_for_each_child(&session->dev, NULL,
> iscsi_iter_destroy_conn_fn);
next prev parent reply other threads:[~2022-04-14 15:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 1:49 [PATCH 0/2] Fix multiple iscsi session unbind event sent to userspace Wenchao Hao
2022-04-14 1:49 ` [PATCH 1/2] scsi: iscsi: introduce session UNBOUND state to avoid multiple unbind event Wenchao Hao
2022-04-14 15:22 ` Mike Christie
2022-04-15 9:33 ` Wenchao Hao
2022-04-14 1:49 ` [PATCH 2/2] iscsi: set session to FREE state after unbind session in remove session Wenchao Hao
2022-04-14 15:30 ` Mike Christie [this message]
2022-04-15 9:40 ` Wenchao Hao
2022-04-15 15:17 ` Mike Christie
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=a8087705-2cea-f01c-ce67-639e97edc30a@oracle.com \
--to=michael.christie@oracle.com \
--cc=cleech@redhat.com \
--cc=haowenchao@huawei.com \
--cc=jejb@linux.ibm.com \
--cc=lduncan@suse.com \
--cc=linfeilong@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=open-iscsi@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®