public inbox for linux-block@vger.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 6.14-rc6
Date: Fri, 7 Mar 2025 07:25:59 -0700	[thread overview]
Message-ID: <d14d2623-6d7c-46fd-865b-c2334439eee8@kernel.dk> (raw)

Hi Linus,

Set of block fixes that should go into the 6.14-rc6 kernel release. This
pull request contains:

- NVMe pull request via Keith
	- TCP use after free fix on polling (Sagi)
	- Controller memory buffer cleanup fixes (Icenowy)
	- Free leaking requests on bad user passthrough commands (Keith)
	- TCP error message fix (Maurizio)
	- TCP corruption fix on partial PDU (Maurizio)
	- TCP memory ordering fix for weakly ordered archs (Meir)
	- Type coercion fix on message error for TCP (Dan)

- Name the RQF flags enum, fixing issues with anon enums and BPF import
  of it.

- ublk parameter setting fix.

- GPT partition 7-bit conversion fix.

Please pull!


The following changes since commit b654f7a51ffb386131de42aa98ed831f8c126546:

  block: fix 'kmem_cache of name 'bio-108' already exists' (2025-02-28 07:06:42 -0700)

are available in the Git repository at:

  git://git.kernel.dk/linux.git tags/block-6.14-20250306

for you to fetch changes up to e7112524e5e885181cc5ae4d258f33b9dbe0b907:

  block: Name the RQF flags enum (2025-03-06 17:50:55 -0700)

----------------------------------------------------------------
block-6.14-20250306

----------------------------------------------------------------
Breno Leitao (1):
      block: Name the RQF flags enum

Dan Carpenter (1):
      nvme-tcp: fix signedness bug in nvme_tcp_init_connection()

Icenowy Zheng (2):
      nvme-pci: clean up CMBMSC when registering CMB fails
      nvme-pci: skip CMB blocks incompatible with PCI P2P DMA

Jens Axboe (1):
      Merge tag 'nvme-6.14-2025-03-05' of git://git.infradead.org/nvme into block-6.14

Keith Busch (1):
      nvme-ioctl: fix leaked requests on mapping error

Maurizio Lombardi (3):
      nvmet: remove old function prototype
      nvme-tcp: Fix a C2HTermReq error message
      nvme-tcp: fix potential memory corruption in nvme_tcp_recv_pdu()

Meir Elisha (1):
      nvmet-tcp: Fix a possible sporadic response drops in weakly ordered arch

Olivier Gayot (1):
      block: fix conversion of GPT partition name to 7-bit

Sagi Grimberg (1):
      nvme-tcp: fix possible UAF in nvme_tcp_poll

Uday Shankar (1):
      ublk: set_params: properly check if parameters can be applied

 block/partitions/efi.c      |  2 +-
 drivers/block/ublk_drv.c    |  7 +++++--
 drivers/nvme/host/ioctl.c   | 12 ++++++++----
 drivers/nvme/host/pci.c     | 21 +++++++++++++--------
 drivers/nvme/host/tcp.c     | 45 ++++++++++++++++++++++++++++++++++++---------
 drivers/nvme/target/nvmet.h |  1 -
 drivers/nvme/target/tcp.c   | 15 +++++++++++----
 include/linux/blk-mq.h      |  2 +-
 8 files changed, 75 insertions(+), 30 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2025-03-07 14:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-07 14:25 Jens Axboe [this message]
2025-03-07 22:30 ` [GIT PULL] Block fixes for 6.14-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=d14d2623-6d7c-46fd-865b-c2334439eee8@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