From: Keith Busch <kbusch@kernel.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-nvme@lists.infradead.org, hch@lst.de, sagi@grimberg.me,
kch@nvidia.com
Subject: Re: [GIT PULL] nvme updates for Linux 7.3
Date: Thu, 13 Aug 2026 14:27:36 -0600 [thread overview]
Message-ID: <an4ouLiJRHmsP3wv@kbusch-mbp> (raw)
In-Reply-To: <c5f8232a-1e52-464d-93c6-f2c91a403f97@kernel.dk>
On Thu, Aug 13, 2026 at 12:36:32PM -0600, Jens Axboe wrote:
> On 8/13/26 11:46 AM, Keith Busch wrote:
> > The following changes since commit f01f5275feb77bac9fefbbf7cc584fe0b3850a92:
> >
> > ublk: snapshot batch commands before preparing I/O (2026-07-02 06:25:21 -0600)
> >
> > are available in the Git repository at:
> >
> > git://git.infradead.org/nvme.git tags/nvme-7.3-2026-08-13
> >
> > for you to fetch changes up to f1a8846e06388113dfdbb89dee005083fa9afdf9:
> >
> > nvmet: fix max_qid race between configfs and controller allocation (2026-08-13 09:26:44 -0700)
> >
> > ----------------------------------------------------------------
> > nvme updates for Linux 7.3
>
> I think we deserve a better summary than that... What's in this PR?
Sure, I'll push a new tag.
The bulk of this is a collection of bug fixes largely found through
fuzzers and AI for both host and target mode. Many of these address
conditions after receiving protocol invalid payloads that could have
caused the driver to access out-of-bounds memory. The remaining
fixes properly handle cleanups in error paths that may either leak
resources or trigger a use-after-free.
The other large chunk from Nilay adds context annotations for compile
time checks.
prev parent reply other threads:[~2026-08-13 20:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 17:46 [GIT PULL] nvme updates for Linux 7.3 Keith Busch
2026-08-13 18:36 ` Jens Axboe
2026-08-13 20:27 ` Keith Busch [this message]
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=an4ouLiJRHmsP3wv@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kch@nvidia.com \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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.