From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: "hare@suse.de" <hare@suse.de>
Cc: "kbusch@kernel.org" <kbusch@kernel.org>,
"hch@lst.de" <hch@lst.de>, "sagi@grimberg.me" <sagi@grimberg.me>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH 0/3] nvme-fabrics: add post connect auth code helper
Date: Thu, 18 Apr 2024 04:24:31 +0000 [thread overview]
Message-ID: <374b839f-49ea-4d0b-bbf5-b711f4854862@nvidia.com> (raw)
In-Reply-To: <e8a819fd-3e40-47dc-8ad1-1932d7a271e3@nvidia.com>
On 4/15/24 20:53, Chaitanya Kulkarni wrote:
> On 2/7/24 22:24, Chaitanya Kulkarni wrote:
>> Hi,
>>
>> Post connect command authentication handling code is repeated into in
>> nvmf_connect_admin_queue() and nvmf_connect_io_queue(). Moreover this
>> code actully belongs to authentication and should not be a part of
>> common code.
>>
>> Add a helper to handle post connect command authentication. Use the
>> same helper in nvmf_connect_[admin|io]_queue(). This also removes
>> authentication specific code from a build where authentication feature
>> is not configured.
>>
>> I've tested the code with and without NVME_AUTH configured with blktests
>> they are passing. Below is a detailed log.
>>
>> -ck
>>
>> Chaitanya Kulkarni (3):
>> nvme-fabrics: factor out auth code into helper
>> nvme-fabrics: use post connect auth helper
>> nvme-auth: unexport negotiate and wait functions
>>
>> drivers/nvme/host/auth.c | 38 +++++++++++++++++++++++++---
>> drivers/nvme/host/fabrics.c | 50 ++-----------------------------------
>> drivers/nvme/host/nvme.h | 16 ++++++------
>> 3 files changed, 43 insertions(+), 61 deletions(-)
>>
>>
> Can someone please look into this series ? this remove unnecessary code
> sitting in the fabrics that should be a part of authentication ...
>
> -ck
>
>
gentle ping, can I get some feedback if this is not needed for any reason ?
-ck
prev parent reply other threads:[~2024-04-18 4:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 6:24 [PATCH 0/3] nvme-fabrics: add post connect auth code helper Chaitanya Kulkarni
2024-02-08 6:24 ` [PATCH 1/3] nvme-fabrics: factor out auth code into helper Chaitanya Kulkarni
2024-04-18 9:30 ` Sagi Grimberg
2024-04-23 19:57 ` Chaitanya Kulkarni
2024-05-23 9:35 ` Hannes Reinecke
2024-02-08 6:24 ` [PATCH 2/3] nvme-fabrics: use post connect auth helper Chaitanya Kulkarni
2024-04-18 9:31 ` Sagi Grimberg
2024-05-23 9:39 ` Hannes Reinecke
2024-02-08 6:24 ` [PATCH 3/3] nvme-auth: unexport negotiate and wait functions Chaitanya Kulkarni
2024-04-18 9:32 ` Sagi Grimberg
2024-05-23 9:40 ` Hannes Reinecke
2024-04-16 3:53 ` [PATCH 0/3] nvme-fabrics: add post connect auth code helper Chaitanya Kulkarni
2024-04-18 4:24 ` Chaitanya Kulkarni [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=374b839f-49ea-4d0b-bbf5-b711f4854862@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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