From: Keith Busch <kbusch@kernel.org>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: linux-nvme@lists.infradead.org, Christoph Hellwig <hch@lst.de>,
Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
Subject: Re: [PATCH] nvmet: fix a memory leak in controller identify
Date: Fri, 24 Jan 2025 08:35:51 -0700 [thread overview]
Message-ID: <Z5OzV2_xFIeWeuIC@kbusch-mbp> (raw)
In-Reply-To: <20250124110033.391731-1-sagi@grimberg.me>
On Fri, Jan 24, 2025 at 01:00:33PM +0200, Sagi Grimberg wrote:
> Simply free an allocated buffer once we copied its content
> to the request sgl.
Thanks, applied to nvme-6.14.
next prev parent reply other threads:[~2025-01-24 15:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 11:00 [PATCH] nvmet: fix a memory leak in controller identify Sagi Grimberg
2025-01-24 14:13 ` Nilay Shroff
2025-01-24 15:35 ` Keith Busch [this message]
2025-01-27 7:11 ` 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=Z5OzV2_xFIeWeuIC@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=hch@lst.de \
--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