Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 7.2
Date: Tue, 23 Jun 2026 08:47:34 -0600	[thread overview]
Message-ID: <ajqchuQAz534Erac@kbusch-mbp> (raw)

The following changes since commit 7ed4aab1381f3439f45032eb860f89d9da5e45c2:

  block: optimize I/O merge hot path with unlikely() hints (2026-06-08 07:46:58 -0600)

are available in the Git repository at:

  git://git.infradead.org/nvme.git tags/nvme-7.2-2026-06-23

for you to fetch changes up to 7d953c75f0a3f905aadf3675c9394a5b9d9897bf:

  nvmet-tcp: handle TCP_CLOSING state in nvmet_tcp_state_change (2026-06-10 08:14:19 -0700)

----------------------------------------------------------------
nvme fixes for Linux 7.2

 - Apple A11 quirk for sharing tags across admin and IO queues (Nick)
 - Target fix for short AUTH_RECEIVE buffers (Michael)
 - Target fix for SQ refcount leak (Wentao)
 - Target RDMA handling inline data with nonzero offset (Bryam)
 - Target TCP fix handling the TCP_CLOSING state (Maurizio)
 - FC abort fixes in early initialization (Mohamed)
 - Controller device teardown fixes (Maurizio, John)
 - Allocate the target ana_state with the port (Rosen)
 - Quieten sparse and sysfs symbol warnings (John)

----------------------------------------------------------------
Bryam Vargas (1):
      nvmet-rdma: handle inline data with a nonzero offset

John Garry (3):
      nvme: quieten sparse warning in valid LBA size check
      nvme: make some sysfs diagnostic structures static
      nvme: make nvme_add_ns{_head}_cdev return void

Maurizio Lombardi (2):
      nvme: fix crash and memory leak during invalid cdev teardown
      nvmet-tcp: handle TCP_CLOSING state in nvmet_tcp_state_change

Michael Bommarito (1):
      nvmet-auth: reject short AUTH_RECEIVE buffers

Mohamed Khalfella (1):
      nvme-fc: Do not cancel requests in io target before it is initialized

Nick Chan (1):
      nvme-apple: Prevent shared tags across queues on Apple A11

Rosen Penev (1):
      nvme: target: allocate ana_state with port

Wentao Liang (1):
      nvmet: fix refcount leak in nvmet_sq_create()

 drivers/nvme/host/apple.c              | 12 +++------
 drivers/nvme/host/core.c               | 45 ++++++++++++++++++++++------------
 drivers/nvme/host/fc.c                 |  7 +++++-
 drivers/nvme/host/multipath.c          | 24 ++++++++++--------
 drivers/nvme/host/nvme.h               |  5 +++-
 drivers/nvme/host/sysfs.c              |  6 ++---
 drivers/nvme/target/configfs.c         |  9 +------
 drivers/nvme/target/core.c             |  2 +-
 drivers/nvme/target/fabrics-cmd-auth.c | 26 +++++++++++++++++++-
 drivers/nvme/target/nvmet.h            |  2 +-
 drivers/nvme/target/rdma.c             | 18 ++++++++------
 drivers/nvme/target/tcp.c              |  1 +
 12 files changed, 100 insertions(+), 57 deletions(-)



             reply	other threads:[~2026-06-23 14:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-23 14:47 Keith Busch [this message]
2026-06-23 15:06 ` [GIT PULL] nvme fixes for Linux 7.2 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=ajqchuQAz534Erac@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