public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@kernel.org>
To: axboe@kernel.dk
Cc: linux-nvme@lists.infradead.org, hch@lst.de, sagi@grimberg.me
Subject: [GIT PULL] nvme fixes for Linux 7.0
Date: Wed, 4 Mar 2026 08:10:37 -0700	[thread overview]
Message-ID: <aahLbUJOav9p1mfx@kbusch-mbp> (raw)

The following changes since commit 91e1c1bcf0f2376f40ac859cf17d0a64a605e662:

  block, nvme: remove unused dma_iova_state function parameter (2026-01-13 07:23:39 -0700)

are available in the Git repository at:

  git://git.infradead.org/nvme.git tags/nvme-7.0-2026-03-04

for you to fetch changes up to c3320153769f05fd7fe9d840cb555dd3080ae424:

  nvme: fix memory allocation in nvme_pr_read_keys() (2026-03-04 06:53:41 -0800)

----------------------------------------------------------------
nvme fixes for Linux 7.0

 - Improve quirk visibility and configurability (Maurizio)
 - Fix runtime user modification to queue setup (Keith)
 - Fix multipath leak on try_module_get failure (Keith)
 - Ignore ambiguous spec definitions for better atomics support (John)
 - Fix admin queue leak on controller reset (Ming)
 - Fix large allocation in persistent reservation read keys (Sungwoo Kim)
 - Fix fcloop callback handling (Justin)
 - Securely free DHCHAP secrets (Daniel)
 - Various cleanups and typo fixes (John, Wilfred)

----------------------------------------------------------------
Daniel Hodges (1):
      nvme-fabrics: use kfree_sensitive() for DHCHAP secrets

John Garry (3):
      nvme: stop using AWUPF
      nvme: stop setting namespace gendisk device driver data
      nvme: correct comment about nvme_ns_remove()

Justin Tee (1):
      nvmet-fcloop: Check remoteport port_state before calling done callback

Keith Busch (4):
      nvme-pci: ensure we're polling a polled queue
      nvme-pci: cap queue creation to used queues
      nvme-pci: do not try to add queue maps at runtime
      nvme-multipath: fix leak on try_module_get failure

Maurizio Lombardi (3):
      nvme: expose active quirks in sysfs
      nvme: add support for dynamic quirk configuration via module parameter
      nvme: fix memory leak in quirks_param_set()

Ming Lei (1):
      nvme: fix admin queue leak on controller reset

Sungwoo Kim (1):
      nvme: fix memory allocation in nvme_pr_read_keys()

Wilfred Mallawa (1):
      nvme/host: fixup some typos

 Documentation/admin-guide/kernel-parameters.txt |  13 ++
 drivers/nvme/host/core.c                        |  28 ++--
 drivers/nvme/host/fabrics.c                     |   4 +-
 drivers/nvme/host/multipath.c                   |  14 +-
 drivers/nvme/host/nvme.h                        |  57 +++++++-
 drivers/nvme/host/pci.c                         | 186 +++++++++++++++++++++++-
 drivers/nvme/host/pr.c                          |   4 +-
 drivers/nvme/host/sysfs.c                       |  23 +++
 drivers/nvme/host/tcp.c                         |   5 +-
 drivers/nvme/target/fcloop.c                    |  15 +-
 10 files changed, 312 insertions(+), 37 deletions(-)


             reply	other threads:[~2026-03-04 15:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-04 15:10 Keith Busch [this message]
2026-03-04 15:16 ` [GIT PULL] nvme fixes for Linux 7.0 Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2026-03-12 21:07 Keith Busch
2026-03-12 21:16 ` 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=aahLbUJOav9p1mfx@kbusch-mbp \
    --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