From: Wenchao Hao <haowenchao@huawei.com>
To: Mike Christie <michael.christie@oracle.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>, Wenchao Hao <haowenchao@huawei.com>
Subject: [PATCH 0/2] Fix multiple iscsi session unbind event sent to userspace
Date: Wed, 13 Apr 2022 21:49:45 -0400 [thread overview]
Message-ID: <20220414014947.4168447-1-haowenchao@huawei.com> (raw)
kernel would send ISCSI_KEVENT_UNBIND_SESSION twice to userspace, for
open-iscsi, this would trigger iscsi_stop twice. We should fix this issue.
Here introduced a new session state ISCSI_SESSION_UNBOUND to address it.
Once session state is ISCSI_KEVENT_UNBIND_SESSION, it means
__iscsi_unbind_session() has been called for this session and do not need
to execute any more.
Reference:https://github.com/open-iscsi/open-iscsi/issues/338
Wenchao Hao (2):
scsi: iscsi: introduce session UNBOUND state to avoid multiple unbind
event
iscsi: set session to FREE state after unbind session in remove
session
drivers/scsi/scsi_transport_iscsi.c | 45 +++++++++++++++++++++--------
include/scsi/scsi_transport_iscsi.h | 1 +
2 files changed, 34 insertions(+), 12 deletions(-)
--
2.32.0
next reply other threads:[~2022-04-13 12:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 1:49 Wenchao Hao [this message]
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
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=20220414014947.4168447-1-haowenchao@huawei.com \
--to=haowenchao@huawei.com \
--cc=cleech@redhat.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=michael.christie@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;
as well as URLs for NNTP newsgroup(s).