From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>, Keith Busch <kbusch@kernel.org>,
Sagi Grimberg <sagi@grimberg.me>,
Chaitanya Kulkarni <kch@nvidia.com>
Cc: linux-block@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: [GIT PULL] nvmes fixes for Linux 6.1
Date: Thu, 10 Nov 2022 11:01:07 +0100 [thread overview]
Message-ID: <Y2zL45ll7KIIc0zF@infradead.org> (raw)
The following changes since commit f829230dd51974c1f4478900ed30bb77ba530b40:
block: sed-opal: kmalloc the cmd/resp buffers (2022-11-08 07:14:35 -0700)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-6.1-2022-11-10
for you to fetch changes up to e65fdf530f55c5e387db14470a59a399faa29613:
nvmet: fix a memory leak (2022-11-09 14:29:13 +0100)
----------------------------------------------------------------
nvme fixes for Linux 6.1
- quiet user passthrough command errors (Keith Busch)
- fix memory leak in nvmet_subsys_attr_model_store_locked
- fix a memory leak in nvmet-auth (Sagi Grimberg)
----------------------------------------------------------------
Aleksandr Miloserdov (1):
nvmet: fix memory leak in nvmet_subsys_attr_model_store_locked
Keith Busch (1):
nvme: quiet user passthrough command errors
Sagi Grimberg (1):
nvmet: fix a memory leak
drivers/nvme/host/core.c | 3 +--
drivers/nvme/host/pci.c | 2 --
drivers/nvme/target/configfs.c | 8 ++++++--
3 files changed, 7 insertions(+), 6 deletions(-)
next reply other threads:[~2022-11-10 10:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 10:01 Christoph Hellwig [this message]
2022-11-10 13:55 ` [GIT PULL] nvmes fixes for Linux 6.1 Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2022-11-18 12:31 Christoph Hellwig
2022-11-18 14:48 ` Jens Axboe
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=Y2zL45ll7KIIc0zF@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--cc=linux-block@vger.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;
as well as URLs for NNTP newsgroup(s).