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>,
<james.smart@broadcom.com>, Keith Busch <kbusch@kernel.org>
Subject: [PATCHv2 0/5] nvme: fix initialization memleak
Date: Tue, 4 Jun 2024 11:59:03 -0700 [thread overview]
Message-ID: <20240604185908.3703052-1-kbusch@meta.com> (raw)
From: Keith Busch <kbusch@kernel.org>
I ran more of the blktests on loop in addtion to pci, also did more
error injection at various points around the early initialization to
make sure the kmemleak really is gone.
Changes since v1:
Use ERR_CAST() as appropriate (Christoph, Hannes)
Fix apple cleanup error (me)
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 | 32 +++++++++++++++++----
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, 155 insertions(+), 57 deletions(-)
--
2.43.0
next reply other threads:[~2024-06-04 18:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 18:59 Keith Busch [this message]
2024-06-04 18:59 ` [PATCHv2 1/5] nvme: apple: fix device reference counting Keith Busch
2024-06-04 18:59 ` [PATCHv2 2/5] nvme: tcp: split controller bringup handling Keith Busch
2024-06-04 18:59 ` [PATCHv2 3/5] nvme: rdma: " Keith Busch
2024-06-04 18:59 ` [PATCHv2 4/5] nvme: fc: " Keith Busch
2024-06-04 18:59 ` [PATCHv2 5/5] nvme: split device add from initialization Keith Busch
2024-06-06 12:13 ` Yi Zhang
2024-06-05 1:09 ` [PATCHv2 0/5] nvme: fix initialization memleak Chaitanya Kulkarni
2024-06-05 7:26 ` Christoph Hellwig
2024-06-06 7:33 ` 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=20240604185908.3703052-1-kbusch@meta.com \
--to=kbusch@meta.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=james.smart@broadcom.com \
--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