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.19-rc6
Date: Fri, 16 Jan 2026 20:53:03 -0700	[thread overview]
Message-ID: <4e5e1aba-adc4-4414-bc86-35d3c8d9f653@kernel.dk> (raw)

Hi Linus,

Fix for the block area that should go into this kernel release. This
pull request contains:

- NVMe pull request via Keith
	- Device quirk to disable faulty temperature (Ilikara)
	- TCP target null pointer fix from bad host protocol usage
	  (Shivam)
	- Add apple,t8103-nvme-ans2 as a compatible apple controller
	  (Janne)
	- FC tagset leak fix (Chaitanya)
	- TCP socket deadlock fix (Hannes)
	- Target name buffer overrun fix (Shin'ichiro)

- Fix for an underflow for rnbd during device unmap

- Zero the non-PI part of the auto integrity buffer

- Fix for a configfs memory leak in the null block driver

Please pull!


The following changes since commit f0d385f6689f37a2828c686fb279121df006b4cb:

  ublk: fix use-after-free in ublk_partition_scan_work (2026-01-09 06:55:30 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git tags/block-6.19-20260116

for you to fetch changes up to ec19ed2b3e2af8ec5380400cdee9cb6560144506:

  rnbd-clt: fix refcount underflow in device unmap path (2026-01-15 07:22:09 -0700)

----------------------------------------------------------------
block-6.19-20260116

----------------------------------------------------------------
Caleb Sander Mateos (1):
      block: zero non-PI portion of auto integrity buffer

Chaitanya Kulkarni (2):
      nvme-fc: release admin tagset if init fails
      rnbd-clt: fix refcount underflow in device unmap path

Hannes Reinecke (1):
      nvmet-tcp: fixup hang in nvmet_tcp_listen_data_ready()

Ilikara Zheng (1):
      nvme-pci: disable secondary temp for Wodposit WPBSNM8

Janne Grunau (1):
      nvme-apple: add "apple,t8103-nvme-ans2" as compatible

Jens Axboe (1):
      Merge tag 'nvme-6.19-2026-01-14' of git://git.infradead.org/nvme into block-6.19

Nilay Shroff (2):
      null_blk: fix kmemleak by releasing references to fault configfs items
      nvme: fix PCIe subsystem reset controller state transition

Shin'ichiro Kawasaki (1):
      nvmet: do not copy beyond sybsysnqn string length

Shivam Kumar (1):
      nvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec

 block/bio-integrity-auto.c     |  2 +-
 drivers/block/null_blk/main.c  | 12 +++++++++++-
 drivers/block/rnbd/rnbd-clt.c  |  1 -
 drivers/nvme/host/apple.c      |  1 +
 drivers/nvme/host/fc.c         |  2 ++
 drivers/nvme/host/pci.c        |  7 ++++++-
 drivers/nvme/target/passthru.c |  2 +-
 drivers/nvme/target/tcp.c      | 21 ++++++++++++++++-----
 8 files changed, 38 insertions(+), 10 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2026-01-17  3:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-17  3:53 Jens Axboe [this message]
2026-01-17  5:00 ` [GIT PULL] Block fixes for 6.19-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=4e5e1aba-adc4-4414-bc86-35d3c8d9f653@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