From: Max Gurtovoy <mgurtovoy@nvidia.com>
To: David Jeffery <djeffery@redhat.com>, linux-rdma@vger.kernel.org
Cc: target-devel@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
Laurence Oberman <loberman@redhat.com>
Subject: Re: [Patch 0/2] iscsit/isert deadlock prevention under heavy I/O
Date: Sun, 13 Mar 2022 11:59:03 +0200 [thread overview]
Message-ID: <b97dd278-eedd-1324-1334-78addee204f9@nvidia.com> (raw)
In-Reply-To: <20220311175713.2344960-1-djeffery@redhat.com>
Hi David,
thanks for the report.
On 3/11/2022 7:57 PM, David Jeffery wrote:
> With fast infiniband networks and rdma through isert, the isert version of
> an iSCSI target can get itself into a deadlock condition from when
> max_cmd_sn updates are pushed to the client versus when commands are fully
> released after rdma completes.
>
> iscsit preallocates a limited number of iscsi_cmd structs used for any
> commands from the initiator. While the iscsi window would normally be
> expected to limit the number used by normal SCSI commands, isert can exceed
> this limit with commands waiting finally completion. max_cmd_sn gets
> incremented and pushed to the client on sending the target's final
> response, but the iscsi_cmd won't be freed for reuse until after all rdma
> is acknowledged as complete.
Please check how we fixed that in NVMf in Sagi's commit:
nvmet-rdma: fix possible bogus dereference under heavy load (commit:
8407879c4e0d77)
Maybe this can be done in isert and will solve this problem in a simpler
way.
is it necessary to change max_cmd_sn ?
>
> This allows more new commands to come in even as older commands are not yet
> released. With enough commands on the initiator wanting to be sent, this can
> result in all iscsi_cmd structs being allocated and used for SCSI commands.
>
> And once all are allocated, isert can deadlock when another new command is
> received. Its receive processing waits for an iscsi_cmd to become available.
> But this also stalls processing of the completions which would result in
> releasing an iscsi_cmd, resulting in a deadlock.
>
> This small patch series prevents this issue by altering when and how
> max_cmd_sn changes are reported to the initiator for isert. It gets delayed
> until iscsi_cmd release instead of when sending a final response.
>
> To prevent failure or large delays for informing the initiator of changes to
> max_cmd_sn, NOPIN is used as a method to inform the initiator should the
> difference between internal max_cmd_sn and what has been passed to the
> initiator grow too large.
>
> David Jeffery (2):
> isert: support for unsolicited NOPIN with no response.
> iscsit: increment max_cmd_sn for isert on command release
>
> drivers/infiniband/ulp/isert/ib_isert.c | 11 ++++++-
> drivers/target/iscsi/iscsi_target.c | 18 +++++------
> drivers/target/iscsi/iscsi_target_device.c | 35 +++++++++++++++++++++-
> drivers/target/iscsi/iscsi_target_login.c | 1 +
> drivers/target/iscsi/iscsi_target_util.c | 5 +++-
> drivers/target/iscsi/iscsi_target_util.h | 1 +
> include/target/iscsi/iscsi_target_core.h | 8 +++++
> include/target/iscsi/iscsi_transport.h | 1 +
> 8 files changed, 68 insertions(+), 12 deletions(-)
>
next prev parent reply other threads:[~2022-03-13 9:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 17:57 [Patch 0/2] iscsit/isert deadlock prevention under heavy I/O David Jeffery
2022-03-11 17:57 ` [PATCH 1/2] isert: support for unsolicited NOPIN with no response David Jeffery
2022-03-11 17:57 ` [PATCH 2/2] iscsit: increment max_cmd_sn for isert on command release David Jeffery
2022-03-11 19:08 ` [Patch 0/2] iscsit/isert deadlock prevention under heavy I/O Laurence Oberman
2022-03-13 9:59 ` Max Gurtovoy [this message]
2022-03-14 13:57 ` David Jeffery
2022-03-14 14:52 ` Max Gurtovoy
2022-03-14 15:55 ` David Jeffery
2022-03-14 17:40 ` Laurence Oberman
2022-03-16 10:38 ` Max Gurtovoy
2022-03-16 13:07 ` Laurence Oberman
2022-03-16 14:39 ` Sagi Grimberg
2022-03-16 15:26 ` Laurence Oberman
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=b97dd278-eedd-1324-1334-78addee204f9@nvidia.com \
--to=mgurtovoy@nvidia.com \
--cc=djeffery@redhat.com \
--cc=linux-rdma@vger.kernel.org \
--cc=loberman@redhat.com \
--cc=sagi@grimberg.me \
--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