From: Jens Axboe <axboe@kernel.dk>
To: Keith Busch <kbusch@kernel.org>
Cc: linux-nvme@lists.infradead.org, hch@lst.de, sagi@grimberg.me
Subject: Re: [GIT PULL] nvme fixes for Linux 7.3
Date: Fri, 4 Sep 2026 05:14:37 -0600 [thread overview]
Message-ID: <01199740-73d0-45ca-a6ed-5c9d0179ce3e@kernel.dk> (raw)
In-Reply-To: <apnk9Uoj1X3PKM-k@kbusch-mbp>
On 9/3/26 3:21 PM, Keith Busch wrote:
> Terribly sorry, the previous message was from a stale tree with the
> wrong SHAs. This is the intended pull request:
>
> The following changes since commit 326d49039c10b65522ac7277b19b9b5c42ed1aeb:
>
> nbd: add pre_defined_connections module parameter for pre-created devices (2026-08-15 20:01:20 -0600)
>
> are available in the Git repository at:
>
> git://git.infradead.org/nvme.git tags/nvme-7.3-2026-09-03
>
> for you to fetch changes up to fd9beb8870736e1c6a0b2351d88a161aaeb2b326:
>
> nvme-tcp.h: drop kernel-doc comments, fix a few descriptions (2026-09-03 14:15:11 -0700)
>
> ----------------------------------------------------------------
> nvme fixes for Linux 7.3
>
> - Harden the tcp host and target against malformed PDUs: reject C2HData
> for a non-read command, bound an over-long PDU before copying it, and
> reject unsolicited H2CData (Yehyeong, Shivam)
> - Fix circular locking on TLS queues (Xixin)
> - Fix a soft lockup when scanning sparse namespace ID space (Mohamed)
> - Fix racy access to the FDP placement id array (Kanchan)
> - RDMA host and target fixes for a double cleanup on the queue_rq
> error path and a queue leak when the connect backlog is exceeded
> (Xixin)
> - Authentication fixes: drain the target's expiry work before the SQ
> is freed, and release the DH-CHAP secret when parsing fails (Kazuki,
> Xu Rao)
> - Fix nvme-fc options double free when nvme_add_ctrl() fails (Niklas)
> - Add missing SRCU grace period to nvme_alloc_ns() error path (Tristan)
> - Skip zoned limits update when the zone info query failed (Chao)
> - Reject enabling a target namespace with no device path (Seokgyu)
> - Add opcode filtering for fault injection (Mohamed)
> - Drop the kernel-doc comments from nvme-tcp.h (Randy)
Pulled, thanks.
--
Jens Axboe
prev parent reply other threads:[~2026-09-04 11:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 21:06 [GIT PULL] nvme fixes for Linux 7.3 Keith Busch
2026-09-03 21:21 ` Keith Busch
2026-09-04 11:14 ` Jens Axboe [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=01199740-73d0-45ca-a6ed-5c9d0179ce3e@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--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.