From: Maurizio Lombardi <mlombard@redhat.com>
To: martin.petersen@oracle.com
Cc: michael.christie@oracle.com, target-devel@vger.kernel.org
Subject: [PATCH V2 0/3] Fix possible hangs and race conditions during login
Date: Mon, 17 Apr 2023 19:17:58 +0200 [thread overview]
Message-ID: <20230417171801.208122-1-mlombard@redhat.com> (raw)
PATCH 1 fixes a possible hang when during a login operation the initiator
stops sending data to the target and the login_work doesn't get scheduled.
PATCH 3 fixes a bug in iscsi_target_locate_portal(), in the error
code path the login semaphore may end up being released even if
no one called down() against it, this may allow
multiple threads to access the semaphore-protected code.
v2: the login timeout of 15 seconds now is relative to the entire
login operation and not per-PDU.
Maurizio Lombardi (3):
target: iscsi: fix hang in the iSCSI login code
target: iscsi: remove unused transport_timer
target: iscsi: prevent login threads from racing between each other
drivers/target/iscsi/iscsi_target.c | 2 -
drivers/target/iscsi/iscsi_target_login.c | 63 ++------------------
drivers/target/iscsi/iscsi_target_nego.c | 72 +++++++++++++----------
drivers/target/iscsi/iscsi_target_util.c | 51 ++++++++++++++++
drivers/target/iscsi/iscsi_target_util.h | 4 ++
include/target/iscsi/iscsi_target_core.h | 7 ++-
6 files changed, 104 insertions(+), 95 deletions(-)
--
2.31.1
next reply other threads:[~2023-04-17 17:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 17:17 Maurizio Lombardi [this message]
2023-04-17 17:17 ` [PATCH V2 1/3] target: iscsi: fix hang in the iSCSI login code Maurizio Lombardi
2023-04-26 15:35 ` Mike Christie
2023-04-26 15:39 ` Mike Christie
2023-04-17 17:18 ` [PATCH V2 2/3] target: iscsi: remove unused transport_timer Maurizio Lombardi
2023-04-26 15:43 ` Mike Christie
2023-04-17 17:18 ` [PATCH V2 3/3] target: iscsi: prevent login threads from racing between each other Maurizio Lombardi
2023-04-26 15:44 ` 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=20230417171801.208122-1-mlombard@redhat.com \
--to=mlombard@redhat.com \
--cc=martin.petersen@oracle.com \
--cc=michael.christie@oracle.com \
--cc=target-devel@vger.kernel.org \
/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