From: Keith Busch <kbusch@kernel.org>
To: axboe@kernel.dk
Cc: hch@lst.de, sagi@grimberg.me, linux-nvme@lists.infradead.org
Subject: [GIT PULL] nvme fixes for Linux 6.13
Date: Thu, 5 Dec 2024 09:10:57 -0800 [thread overview]
Message-ID: <Z1HeockCWHXRcvGb@kbusch-mbp.dhcp.thefacebook.com> (raw)
The following changes since commit ec9b3ac6e5630e320d926ea13a06d86d2a6bdde1:
Merge tag 'nvme-6.13-2024-11-21' of git://git.infradead.org/nvme into for-6.13/block (2024-11-21 10:57:34 -0700)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-6.13-2024-12-05
for you to fetch changes up to b4e12f5728ff963ca5590c48b85a20d076bf517d:
nvme-tcp: simplify nvme_tcp_teardown_io_queues() (2024-12-04 10:15:46 -0800)
----------------------------------------------------------------
nvme fixes for Linux 6.13
- Target fix using incorrect zero buffer (Nilay)
- Device specifc deallocate quirk fixes (Christoph, Keith)
- Fabrics fix for handling max command target bugs (Maurizio)
- Cocci fix usage for kzalloc (Yu-Chen)
- DMA size fix for host memory buffer feature (Christoph)
- Fabrics queue cleanup fixes (Chunguang)
----------------------------------------------------------------
Christoph Hellwig (2):
nvme: don't apply NVME_QUIRK_DEALLOCATE_ZEROES when DSM is not supported
nvme-pci: don't use dma_alloc_noncontiguous with 0 merge boundary
Chunguang.xu (4):
nvme-tcp: fix the memleak while create new ctrl failed
nvme-rdma: unquiesce admin_q before destroy it
nvme-tcp: no need to quiesce admin_q in nvme_tcp_teardown_io_queues()
nvme-tcp: simplify nvme_tcp_teardown_io_queues()
Keith Busch (1):
nvme-pci: remove two deallocate zeroes quirks
Maurizio Lombardi (1):
nvme-fabrics: handle zero MAXCMD without closing the connection
Nilay Shroff (1):
nvmet: use kzalloc instead of ZERO_PAGE in nvme_execute_identify_ns_nvm()
Yu-Chun Lin (1):
nvmet: replace kmalloc + memset with kzalloc for data allocation
drivers/nvme/host/core.c | 8 +++++---
drivers/nvme/host/pci.c | 7 +++----
drivers/nvme/host/rdma.c | 8 +-------
drivers/nvme/host/tcp.c | 17 +++++------------
drivers/nvme/target/admin-cmd.c | 9 +++++++--
drivers/nvme/target/pr.c | 3 +--
6 files changed, 22 insertions(+), 30 deletions(-)
next reply other threads:[~2024-12-05 17:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 17:10 Keith Busch [this message]
2024-12-05 17:15 ` [GIT PULL] nvme fixes for Linux 6.13 Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2024-12-31 17:41 Keith Busch
2024-12-31 17:46 ` 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=Z1HeockCWHXRcvGb@kbusch-mbp.dhcp.thefacebook.com \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--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