From: Keith Busch <kbusch@kernel.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-nvme@lists.infradead.org, hch@lst.de, linux-block@vger.kernel.org
Subject: Re: [GIT PULL] nvme fixes for 6.19, final
Date: Thu, 5 Feb 2026 08:54:17 -0700 [thread overview]
Message-ID: <aYS9KeAYcTh9GIaJ@kbusch-mbp> (raw)
In-Reply-To: <ded8f99f-2d4a-48fc-9cff-02aa317a1c25@kernel.dk>
On Thu, Feb 05, 2026 at 08:49:35AM -0700, Jens Axboe wrote:
> On 2/5/26 8:47 AM, Jens Axboe wrote:
> > On 2/5/26 8:38 AM, Keith Busch wrote:
> >> 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
> >
> > After this one, iod in nvme_pci_prp_iter_next() is now unused, which
> > will trigger a compiler warning...
>
> Actually this is only true in the 7.0 based branches. Should be fine
> for 6.19, I'll add a commit for the 7.0 merge.
Yeah, I initially applied this to 7.0 with it removed, but we decided
this was a nasty and easy to hit bug that 6.19 is better of having fixed
on release. I had to leave the 'iod' in for the 6.19 port, so looks like
we'll have a merge conflict for the next cycle.
next prev parent reply other threads:[~2026-02-05 15:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 15:38 [GIT PULL] nvme fixes for 6.19, final Keith Busch
2026-02-05 15:47 ` 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 [this message]
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=aYS9KeAYcTh9GIaJ@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