public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@kernel.org>
To: axboe@kernel.dk
Cc: linux-nvme@lists.infradead.org, hch@lst.de, linux-block@vger.kernel.org
Subject: [GIT PULL] nvme fixes for 6.19, final
Date: Thu, 5 Feb 2026 08:38:14 -0700	[thread overview]
Message-ID: <aYS5ZlwruxpNCdTL@kbusch-mbp> (raw)

Hi Jens,

Some late fixes for nvme that should go in this release. One for a pci
regression that causes a kernel panic during certain dma conditions. The
other fixes a vulnerability in the tcp target.

The following changes since commit 4da7c5c3ec34d839bba6e035c3d05c447a2f9d4f:

  bcache: fix I/O accounting leak in detached_dev_do_request (2026-01-28 19:06:55 -0700)

are available in the Git repository at:

  git://git.infradead.org/nvme.git tags/nvme-6.19-2026-02-05

for you to fetch changes up to 52a0a98549344ca20ad81a4176d68d28e3c05a5c:

  nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec (2026-02-05 07:29:10 -0800)

----------------------------------------------------------------
nvme fixes for Linux 6.19

 - Fix NULL pointer access setting up dma mappings (Keith)
 - Fix invalid memory access from malformed TCP PDU (YunJe)

----------------------------------------------------------------
Keith Busch (1):
      nvme-pci: handle changing device dma map requirements

YunJe Shin (1):
      nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec

 drivers/nvme/host/pci.c   | 45 ++++++++++++++++++++++++++++++---------------
 drivers/nvme/target/tcp.c | 17 +++++++++++++++++
 2 files changed, 47 insertions(+), 15 deletions(-)

             reply	other threads:[~2026-02-05 15:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-05 15:38 Keith Busch [this message]
2026-02-05 15:47 ` [GIT PULL] nvme fixes for 6.19, final Jens Axboe
2026-02-05 15:49   ` Christoph Hellwig
2026-02-05 15:51     ` Jens Axboe
2026-02-05 15:49   ` Jens Axboe
2026-02-05 15:54     ` Keith Busch
2026-02-05 15:55       ` 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=aYS5ZlwruxpNCdTL@kbusch-mbp \
    --to=kbusch@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.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