linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Chris Leech <cleech@redhat.com>
To: Chaitanya Kulkarni <chaitanyak@nvidia.com>
Cc: Hannes Reinecke <hare@suse.de>,
	 "linux-nvme@lists.infradead.org"
	<linux-nvme@lists.infradead.org>
Subject: Re: [PATCH 1/1] nvme: fix dhchap secret memleaks in auth code
Date: Mon, 22 May 2023 18:21:08 -0700	[thread overview]
Message-ID: <CAPnfmXK3F3W1bhC8Bdn2X0bGdnDs+tJBcCVGV7kvxNgiXsr24g@mail.gmail.com> (raw)
In-Reply-To: <8066e1d6-3197-6127-00b3-a3a2b8eae369@nvidia.com>

On Mon, May 22, 2023 at 5:16 PM Chaitanya Kulkarni
<chaitanyak@nvidia.com> wrote:
> On 5/22/23 14:53, Chris Leech wrote:
> > Re-authentication through the sysfs interface without changing the PSK
> > will result in a memory leak. This was tested with blktests nvme/045.
>
> I think it is already fixed in nvme-6.5, if not please let me know ..

You're right, sorry about that.  Looks good in nvme-6.5

- Chris



      reply	other threads:[~2023-05-23  1:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-22 21:53 [PATCH 1/1] nvme: fix dhchap secret memleaks in auth code Chris Leech
2023-05-23  0:16 ` Chaitanya Kulkarni
2023-05-23  1:21   ` Chris Leech [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=CAPnfmXK3F3W1bhC8Bdn2X0bGdnDs+tJBcCVGV7kvxNgiXsr24g@mail.gmail.com \
    --to=cleech@redhat.com \
    --cc=chaitanyak@nvidia.com \
    --cc=hare@suse.de \
    --cc=linux-nvme@lists.infradead.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 NNTP newsgroup(s).