All of lore.kernel.org
 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-rc2
Date: Sat, 5 Sep 2026 05:21:07 -0600	[thread overview]
Message-ID: <fba0a84a-488f-43b7-b4da-0746180da780@kernel.dk> (raw)

Hi Linus,

Fixes for block that should go into the 7.3-rc2 kernel release. Mostly
NVMe fixes, but also other drivers fixes. This pull request contains:

- NVMe fixes via Keith:
	- nvme-tcp fixes for an out-of-bounds write on an over-long PDU
	- nvmet-tcp, nvmet-rdma and nvme-rdma leak and cleanup-ordering
	  fixes
	- FDP placement id array racy access fix
	- nvme-fc double free of fabrics options on nvme_add_ctrl()
	  failure, and a secret leak failure
	- Fault injection opcode filtering
	- stale namespace removal during scan
	- Various other smaller fixes and cleanups

- Flag zoned disks with GENHD_FL_NO_PART

- Save the page offset gaps in a cloned bio

- Fix dma_alignment for large or unreported limits in loop and zloop

- Clear VM_MAYWRITE on a read-only ublk char device mmap

Please pull!


The following changes since commit cee9395acd8043be0644b25c34bfa86623f2b935:

  Linux 7.3-rc1 (2026-08-30 13:34:40 -0700)

are available in the Git repository at:

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

for you to fetch changes up to 00ef2248c5dae08548f7ceb6951b022f89905330:

  Merge tag 'nvme-7.3-2026-09-03' of git://git.infradead.org/nvme into block-7.3 (2026-09-03 19:48:07 -0600)

----------------------------------------------------------------
block-7.3-20260905

----------------------------------------------------------------
Chao Shi (1):
      nvme: skip the zoned limits update if the zone info query failed

Damien Le Moal (1):
      block: flag zoned disks with GENHD_FL_NO_PART

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

Kanchan Joshi (2):
      nvme: set ns->head in nvme_alloc_ns_head
      nvme: fix racy access to FDP placement id array

Kanishka De Silva (1):
      ublk: clear VM_MAYWRITE on read-only ublk char device mmap

Kazuki Hanai (1):
      nvmet-auth: Synchronize timeout work during SQ teardown

Keith Busch (3):
      block: save page offset gaps in cloned bio
      loop, zloop: fix dma_alignment for large or unreported limits
      MAINTAINERS: update nvme entry

Mohamed Khalfella (4):
      nvme: add opcode filtering for fault injection
      nvme: remove stale namespaces by NSID range during scan
      nvme: print namespace IDs as unsigned 32bit value
      nvmet: print namespace IDs as unsigned 32bit value

Niklas Cassel (1):
      nvme-fc: fix double free of fabrics options when nvme_add_ctrl() fails

Randy Dunlap (1):
      nvme-tcp.h: drop kernel-doc comments, fix a few descriptions

Seokgyu Choi (1):
      nvmet: reject namespace enable without device path

Shivam Kumar (2):
      nvmet-tcp: fix out-of-bounds write when receiving an over-long PDU
      nvmet-tcp: reject unsolicited H2CData PDUs

Tristan Madani (1):
      nvme: add missing SRCU grace period in error path

Xixin Liu (3):
      nvme-rdma: fix -EIO cleanup order in queue_rq
      nvmet-rdma: fix queue leak when connect backlog is exceeded
      nvme-tcp: defer TLS inline send to io_work

Xu Rao (1):
      nvme-fabrics: fix DHCHAP secret leak on parse failure

Yehyeong Lee (2):
      nvme-tcp: check the data direction of a C2HData PDU
      nvme-tcp: return -EPROTO for a C2HData on a write

 .../fault-injection/nvme-fault-injection.rst       | 65 ++++++++++++++
 MAINTAINERS                                        |  2 +-
 block/bio.c                                        |  9 ++
 block/genhd.c                                      |  7 ++
 drivers/block/loop.c                               |  8 +-
 drivers/block/ublk_drv.c                           |  6 ++
 drivers/block/zloop.c                              |  8 +-
 drivers/nvme/host/core.c                           | 99 +++++++++++++---------
 drivers/nvme/host/fabrics.c                        |  2 +
 drivers/nvme/host/fault_inject.c                   | 14 ++-
 drivers/nvme/host/fc.c                             | 26 ++++--
 drivers/nvme/host/nvme.h                           |  2 +
 drivers/nvme/host/rdma.c                           | 18 ++--
 drivers/nvme/host/sysfs.c                          |  2 +-
 drivers/nvme/host/tcp.c                            | 12 +++
 drivers/nvme/host/zns.c                            |  4 +-
 drivers/nvme/target/auth.c                         |  6 ++
 drivers/nvme/target/configfs.c                     |  4 +-
 drivers/nvme/target/core.c                         |  9 +-
 drivers/nvme/target/nvmet.h                        |  2 +
 drivers/nvme/target/pr.c                           |  2 +-
 drivers/nvme/target/rdma.c                         | 15 ++--
 drivers/nvme/target/tcp.c                          | 10 +++
 include/linux/nvme-tcp.h                           | 18 ++--
 24 files changed, 260 insertions(+), 90 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2026-09-05 11:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-05 11:21 Jens Axboe [this message]
2026-09-05 16:36 ` [GIT PULL] Block fixes for 7.3-rc2 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=fba0a84a-488f-43b7-b4da-0746180da780@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.