Linux block layer
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: [GIT PULL] Block fixes for 7.3-rc6
Date: Fri, 2 Oct 2026 08:50:11 -0600	[thread overview]
Message-ID: <4fbdea09-538d-4be2-8492-bca0aa570e15@kernel.dk> (raw)

Hi Linus,

A set of block fixes for this week. Mostly NVMe via a pull from Keith,
but also a few core block and driver fixes. This pull request contains:

- NVMe fixes via Keith:
	- Fix an out-of-bounds write in nvmet_auth_challenge(), where
	  sizeof() on a void pointer undercounted the challenge header and
	  let a short AUTH_RECEIVE buffer pass the check
	- nvme-multipath fixes for an ANA log bounds check underflow, the
	  command effects log lifetime for multipath heads, and only
	  setting BLK_FEAT_ZONED after the zone info is known.
	- nvmet fixes for ns->enabled teardown ordering, rejecting I/O
	  after the percpu ns reference is killed, device path preservation
	  on allocation failure, and too-short SGL segments in pci-epf
	- nvme-tcp: revert the per-socket dynamic lockdep keys, and delay
	  the socket reclassification
	- A DMA pool alignment quirk for the Micron 4100AT
	- Controller state/reset race fixes, and -Wformat-security
	  workarounds

- blk-mq: set RQF_USE_SCHED when the operation is known, and allow
  cached requests to be used for flush operations

- Reject polled dio with user integrity metadata

- Save the IRQ state in blkg_tryget_closest()

- Set the zone write granularity in virtio_blk

- ublk selftest fixes

Please pull!


The following changes since commit 94b1a3ca9b8db3151f1416263704c159a9470da5:

  selftests: ublk: add batch IO cases to recover_03 (2026-09-10 20:19:21 -0600)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git tags/block-7.3-20261002

for you to fetch changes up to 684b413b5483f57c890c171b9400076a0143b918:

  virtio_blk: set the zone write granularity (2026-09-29 12:54:47 -0600)

----------------------------------------------------------------
block-7.3-20261002

----------------------------------------------------------------
Arnd Bergmann (3):
      drbd: remove unused drbd_nl_mcgrps[] array
      nvme: work around -Wformat-security warning
      nvme: work around all -Wformat-security warnings

Bean Huo (1):
      nvme-pci: add NVME_QUIRK_DMAPOOL_ALIGN_512 for Micron 4100AT

Daehyeon Ko (2):
      nvme-multipath: fix underflow in ANA log bounds checks
      nvmet: pci-epf: reject too-short SGL segments

Dirk Gouders (1):
      selftests: ublk: fix unused_result error

Eric Dumazet (1):
      nvme-tcp: delay nvme_tcp_reclassify_socket()

Guixin Liu (2):
      nvmet: copy the hostid into the ctrl before creating PR pc_refs
      nvme-multipath: set BLK_FEAT_ZONED only after the zone info is known

Hao Zhang (1):
      blk-cgroup: save IRQ state in blkg_tryget_closest()

Jens Axboe (1):
      Merge tag 'nvme-7.3-2026-09-25' of git://git.infradead.org/nvme into block-7.3

Julian Sun (1):
      nvmet: preserve device path on allocation failure

Keith Busch (2):
      blk-mq: set RQF_USE_SCHED when the operation is known
      blk-mq: allow cached requests to be used for flush operations

Maurizio Lombardi (2):
      nvme-fc: do not warn on controller removal race
      nvme: do not reset controllers in NVME_CTRL_NEW state

Niklas Cassel (1):
      virtio_blk: set the zone write granularity

Nilay Shroff (2):
      nvmet: defer setting ns->enabled to false in nvmet_ns_disable()
      nvmet: don't allow I/O admission after percpu ns reference is killed

Shin'ichiro Kawasaki (1):
      Revert "nvme-tcp: lockdep: use dynamic lockdep keys per socket instance"

Weiming Shi (1):
      nvmet-auth: fix out-of-bounds write in nvmet_auth_challenge()

Yang Xiuwei (1):
      block: reject polled dio with user integrity metadata

Yao Sang (1):
      nvme: fix command effects log lifetime for multipath heads

 block/blk-cgroup.c                     |  5 +--
 block/blk-mq.c                         | 63 ++++++++++++++++++++--------------
 block/fops.c                           |  5 +++
 block/mq-deadline.c                    |  2 +-
 drivers/block/drbd/drbd_nl_gen.c       |  4 ---
 drivers/block/virtio_blk.c             |  1 +
 drivers/nvme/host/core.c               | 63 +++++++++++++++-------------------
 drivers/nvme/host/fc.c                 |  2 +-
 drivers/nvme/host/multipath.c          | 19 +++++-----
 drivers/nvme/host/nvme.h               |  9 ++---
 drivers/nvme/host/pci.c                |  2 ++
 drivers/nvme/host/sysfs.c              |  4 +--
 drivers/nvme/host/tcp.c                | 39 +++++++--------------
 drivers/nvme/target/configfs.c         |  9 +++--
 drivers/nvme/target/core.c             | 33 +++++++++++-------
 drivers/nvme/target/fabrics-cmd-auth.c |  2 +-
 drivers/nvme/target/nvmet.h            |  2 ++
 drivers/nvme/target/pci-epf.c          |  3 ++
 tools/testing/selftests/ublk/kublk.c   |  2 +-
 19 files changed, 139 insertions(+), 130 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2026-10-02 14:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02 14:50 Jens Axboe [this message]
2026-10-02 19:31 ` [GIT PULL] Block fixes for 7.3-rc6 pr-tracker-bot

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=4fbdea09-538d-4be2-8492-bca0aa570e15@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=torvalds@linux-foundation.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