Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Martin George <martinus.gpy@gmail.com>
To: Hannes Reinecke <hare@suse.de>,
	linux-nvme@lists.infradead.org,  kbusch@kernel.org, hch@lst.de,
	sagi@grimberg.me
Cc: hare@kernel.org, Prashanth Adurthi <prashana@netapp.com>
Subject: Re: [PATCH v2] nvme-auth: update sc_c in host response
Date: Tue, 23 Sep 2025 00:44:52 +0530	[thread overview]
Message-ID: <a74d50723816faa5902fe08b42dc70e74b8c0ca5.camel@gmail.com> (raw)
In-Reply-To: <8638a12a5f221b874bb0ec54a5b0bf1bdc31131b.camel@gmail.com>

On Tue, 2025-09-16 at 17:11 +0530, Martin George wrote:
> On Tue, 2025-09-09 at 08:43 +0200, Hannes Reinecke wrote:
> > On 9/8/25 19:24, Martin George wrote:
> > > The sc_c field is currently not updated in the host response to
> > > the
> > > controller challenge leading to failures while attempting secure
> > > channel concatenation. Fix this by adding a new sc_c variable to
> > > the
> > > dhchap queue context structure which is appropriately set during
> > > negotiate and then used in the host response.
> > > 
> > > Fixes: e88a7595b57f ("nvme-tcp: request secure channel
> > > concatenation")
> > > Signed-off-by: Martin George <marting@netapp.com>
> > > Signed-off-by: Prashanth Adurthi <prashana@netapp.com>
> > > ---
> > > Changes in v2: set *buf to sc_c as suggested by Hannes
> > > ---
> > >   drivers/nvme/host/auth.c | 6 +++++-
> > >   1 file changed, 5 insertions(+), 1 deletion(-)
> > > 
> > Reviewed-by: Hannes Reinecke <hare@suse.de>
> > 
> > Cheers,
> > 
> > Hannes
> 
> Gentle ping

Pinging again. Please review and provide feedback if any. Thanks.

-Martin



  reply	other threads:[~2025-09-22 19:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-08 17:24 [PATCH v2] nvme-auth: update sc_c in host response Martin George
2025-09-09  6:43 ` Hannes Reinecke
2025-09-16 11:41   ` Martin George
2025-09-22 19:14     ` Martin George [this message]
2025-10-20  8:50 ` Shinichiro Kawasaki
2025-10-21  6:49   ` Hannes Reinecke

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=a74d50723816faa5902fe08b42dc70e74b8c0ca5.camel@gmail.com \
    --to=martinus.gpy@gmail.com \
    --cc=hare@kernel.org \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=prashana@netapp.com \
    --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