From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Maurizio Lombardi <mlombard@redhat.com>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
michael.christie@oracle.com, target-devel@vger.kernel.org
Subject: Re: [PATCH V3 0/3] Fix possible hangs and race conditions during login
Date: Mon, 22 May 2023 18:45:39 -0400 [thread overview]
Message-ID: <168479546537.1263525.11716567178385507185.b4-ty@oracle.com> (raw)
In-Reply-To: <20230508162219.1731964-1-mlombard@redhat.com>
On Mon, 08 May 2023 18:22:16 +0200, Maurizio Lombardi wrote:
> 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.
>
> [...]
Applied to 6.4/scsi-fixes, thanks!
[1/3] target: iscsi: fix hang in the iSCSI login code
https://git.kernel.org/mkp/scsi/c/13247018d68f
[2/3] target: iscsi: remove unused transport_timer
https://git.kernel.org/mkp/scsi/c/98a8c2bf938a
[3/3] target: iscsi: prevent login threads from racing between each other
https://git.kernel.org/mkp/scsi/c/2a737d3b8c79
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2023-05-22 22:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 16:22 [PATCH V3 0/3] Fix possible hangs and race conditions during login Maurizio Lombardi
2023-05-08 16:22 ` [PATCH V3 1/3] target: iscsi: fix hang in the iSCSI login code Maurizio Lombardi
2023-05-08 16:22 ` [PATCH V3 2/3] target: iscsi: remove unused transport_timer Maurizio Lombardi
2023-05-08 16:22 ` [PATCH V3 3/3] target: iscsi: prevent login threads from racing between each other Maurizio Lombardi
2023-05-20 17:42 ` [PATCH V3 0/3] Fix possible hangs and race conditions during login Mike Christie
2023-05-22 22:45 ` Martin K. Petersen [this message]
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=168479546537.1263525.11716567178385507185.b4-ty@oracle.com \
--to=martin.petersen@oracle.com \
--cc=michael.christie@oracle.com \
--cc=mlombard@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).