From: Keith Busch <kbusch@meta.com>
To: <linux-nvme@lists.infradead.org>
Cc: <hch@lst.de>, <sagi@grimberg.me>, <mlombard@redhat.com>,
<hare@suse.de>, <shinichiro.kawasaki@wdc.com>,
Keith Busch <kbusch@kernel.org>
Subject: [PATCH-RFC 0/5] nvme: fix initialization memleak
Date: Mon, 3 Jun 2024 16:05:18 -0700 [thread overview]
Message-ID: <20240603230524.3854115-1-kbusch@meta.com> (raw)
From: Keith Busch <kbusch@kernel.org>
The pci driver is the only one runtime tested. Everything else is
compile tested, except for apple.
Keith Busch (5):
nvme: apple: fix device reference counting
nvme: tcp: split controller bringup handling
nvme: rdma: split controller bringup handling
nvme: fc: split controller bringup handling
nvme: split device add from initialzation
drivers/nvme/host/apple.c | 31 ++++++++++++++++----
drivers/nvme/host/core.c | 58 +++++++++++++++++++++++---------------
drivers/nvme/host/fc.c | 48 ++++++++++++++++++++-----------
drivers/nvme/host/nvme.h | 1 +
drivers/nvme/host/pci.c | 5 ++++
drivers/nvme/host/rdma.c | 33 +++++++++++++++++-----
drivers/nvme/host/tcp.c | 30 ++++++++++++++++----
drivers/nvme/target/loop.c | 5 ++++
8 files changed, 154 insertions(+), 57 deletions(-)
--
2.43.0
next reply other threads:[~2024-06-03 23:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 23:05 Keith Busch [this message]
2024-06-03 23:05 ` [PATCH-RFC 1/5] nvme: apple: fix device reference counting Keith Busch
2024-06-03 23:17 ` Keith Busch
2024-06-03 23:05 ` [PATCH-RFC 2/5] nvme: tcp: split controller bringup handling Keith Busch
2024-06-04 0:35 ` Caleb Sander
2024-06-04 2:44 ` Keith Busch
2024-06-04 4:23 ` Christoph Hellwig
2024-06-04 6:47 ` Hannes Reinecke
2024-06-03 23:05 ` [PATCH-RFC 3/5] nvme: rdma: " Keith Busch
2024-06-03 23:05 ` [PATCH-RFC 4/5] nvme: fc: " Keith Busch
2024-06-03 23:05 ` [PATCH-RFC 5/5] nvme: split device add from initialzation Keith Busch
2024-06-04 4:24 ` [PATCH-RFC 0/5] nvme: fix initialization memleak Christoph Hellwig
2024-06-04 14:51 ` Sagi Grimberg
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=20240603230524.3854115-1-kbusch@meta.com \
--to=kbusch@meta.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mlombard@redhat.com \
--cc=sagi@grimberg.me \
--cc=shinichiro.kawasaki@wdc.com \
/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