From: Leon Romanovsky <leon@kernel.org>
To: Sergey Gorenko <sergeygo@nvidia.com>
Cc: Sagi Grimberg <sagi@grimberg.me>,
linux-rdma@vger.kernel.org, Max Gurtovoy <mgurtovoy@nvidia.com>
Subject: Re: [PATCH] IB/iser: Fix login with authentication
Date: Tue, 16 Aug 2022 15:57:07 +0300 [thread overview]
Message-ID: <YvuUI/RCpJSH8Lo7@unreal> (raw)
In-Reply-To: <20220805060135.18493-1-sergeygo@nvidia.com>
On Fri, Aug 05, 2022 at 09:01:35AM +0300, Sergey Gorenko wrote:
> The iSER Initiator uses two types of receive buffers:
>
> - one big login buffer posted by iser_post_recvl();
> - several small message buffers posted by iser_post_recvm().
>
> The login buffer is used at the login phase and full feature phase in
> the discovery session. It may take a few requests and responses to
> complete the login phase. The message buffers are only used in the
> normal operational session at the full feature phase.
>
> After the commit referred in the fixes line, the login operation fails
> if the authentication is enabled. That happens because the Initiator
> posts a small receive buffer after the first response from Target. So,
> the next send operation fails because Target's second response does not
> fit into the small receive buffer.
>
> This commit adds additional checks to prevent posting small receive
> buffers until the full feature phase.
>
> Fixes: 39b169ea0d36 ("IB/iser: Fix RNR errors")
> Signed-off-by: Sergey Gorenko <sergeygo@nvidia.com>
> Reviewed-by: Max Gurtovoy <mgurtovoy@nvidia.com>
> ---
> drivers/infiniband/ulp/iser/iser_initiator.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
Thanks, applied to -rc.
prev parent reply other threads:[~2022-08-16 12:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 6:01 [PATCH] IB/iser: Fix login with authentication Sergey Gorenko
2022-08-16 12:57 ` Leon Romanovsky [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=YvuUI/RCpJSH8Lo7@unreal \
--to=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mgurtovoy@nvidia.com \
--cc=sagi@grimberg.me \
--cc=sergeygo@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.