[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <daa60cf0-0dde-ea2d-211a-70a9e0efc1b8@oracle.com>
Date: Fri, 21 Oct 2022 12:24:04 -0500
From: Mike Christie <michael.christie@...cle.com>
To: Wenchao Hao <haowenchao@...wei.com>, Lee Duncan <lduncan@...e.com>,
Chris Leech <cleech@...hat.com>,
"James E . J . Bottomley" <jejb@...ux.ibm.com>,
"Martin K . Petersen" <martin.petersen@...cle.com>,
linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: Steffen Maier <maier@...ux.ibm.com>, liuzhiqiang26@...wei.com,
linfeilong@...wei.com
Subject: Re: [PATCH v4] scsi:iscsi: Fix multiple iscsi session unbind event
sent to userspace
On 10/21/22 6:57 PM, Wenchao Hao wrote:
> +
> int iscsi_session_chkready(struct iscsi_cls_session *session)
> {
> int err;
> @@ -1899,6 +1922,7 @@ static void __iscsi_unblock_session(struct work_struct *work)
> cancel_delayed_work_sync(&session->recovery_work);
> spin_lock_irqsave(&session->lock, flags);
> session->state = ISCSI_SESSION_LOGGED_IN;
> + session->target_state = ISCSI_SESSION_TARGET_BOUND;
> spin_unlock_irqrestore(&session->lock, flags);
> /* start IO */
Hey,
Sorry for the late reply.
For the initial login we have not scanned the session above, so there
is no target yet. If iscsid is restarted at this time, then iscsid wants
to sync the session and also do the initial scan.
To handle that case and also better match the state names with the
session's target state we can:
1. Move the above line to iscsi_user_scan_session after we have scanned
the target.
2. Add a new state ISCSI_SESSION_TARGET_ALLOCATED to reflect we have
allocated the target_id, but not yet scanned.
Powered by blists - more mailing lists