From: Keith Busch <kbusch@kernel.org>
To: axboe@kernel.dk
Cc: hch@lst.de, linux-nvme@lists.infradead.org
Subject: [GIT PULL] nvme fixes for 7.3
Date: Mon, 5 Oct 2026 15:18:45 +0200 [thread overview]
Message-ID: <asOjta815QimaDcN@kbusch-mbp> (raw)
Hi Jens,
Sending the nvme PR earlier this week as it doesn't look like I'll have
any other chance for maintenance duties.
The following changes since commit 684b413b5483f57c890c171b9400076a0143b918:
virtio_blk: set the zone write granularity (2026-09-29 12:54:47 -0600)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-7.3-2026-10-05
for you to fetch changes up to 5755f1bd0217ffe3c5cf85467bf6b0680f398265:
Revert "nvme: do not reset controllers in NVME_CTRL_NEW state" (2026-10-05 06:07:37 -0700)
----------------------------------------------------------------
nvme fixes for Linux 7.3
- Fix lock ordering revalidating zoned multipath heads
- Fix swapped ZRASF zone state values for full and read only
- Fix target p2pmem cleanup when the metadata allocation fails
- Fix target status code for invalid NSIDs on reservation features
- Revert the NVME_CTRL_NEW state change, which broke the Apple driver
----------------------------------------------------------------
Guixin Liu (1):
nvmet: return Invalid Field for invalid NSIDs feature 82h
Karl Bonde Torp (1):
nvme: fix swapped ZRASF zone state values for full and read only
Keith Busch (1):
Revert "nvme: do not reset controllers in NVME_CTRL_NEW state"
Palla Raghunath (1):
nvme-multipath: revalidate head zones after unfreezing the head queue
Sang-Hoon Choi (1):
nvmet: use the local P2P device on metadata allocation failure
drivers/nvme/host/core.c | 12 +++++++++++-
drivers/nvme/target/core.c | 2 +-
drivers/nvme/target/pr.c | 4 ++++
include/linux/nvme.h | 4 ++--
4 files changed, 18 insertions(+), 4 deletions(-)
next reply other threads:[~2026-10-05 13:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 13:18 Keith Busch [this message]
2026-10-05 14:47 ` [GIT PULL] nvme fixes for 7.3 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=asOjta815QimaDcN@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-nvme@lists.infradead.org \
/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