From: Keith Busch <kbusch@kernel.org>
To: Shivam Kumar <kumar.shivam43666@gmail.com>
Cc: Greg KH <greg@kroah.com>,
security@kernel.org, hch@lst.de, sagi@grimberg.me,
kch@nvidia.com, linux-nvme@lists.infradead.org,
stable@vger.kernel.org
Subject: Re: [PATCH] nvmet-tcp: reject unsolicited H2CData PDUs
Date: Thu, 27 Aug 2026 15:51:46 -0600 [thread overview]
Message-ID: <apCxcvW33xppjCf_@kbusch-mbp> (raw)
In-Reply-To: <20260827192455.1849385-1-kumar.shivam43666@gmail.com>
On Thu, Aug 27, 2026 at 03:24:55PM -0400, Shivam Kumar wrote:
> nvmet_tcp_handle_h2c_data_pdu() accepts an H2CData PDU after only checking
> that its TTAG is a valid in-range command index and that the command's
> data buffers are mapped. It never checks that the target has actually
> solicited that data by sending an R2T for the command.
Thanks, looks correct. Applied to nvme-7.3.
next prev parent reply other threads:[~2026-08-27 21:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2026082755-stucco-champion-2bb9@gregkh>
2026-08-27 19:24 ` [PATCH] nvmet-tcp: reject unsolicited H2CData PDUs Shivam Kumar
2026-08-27 21:51 ` Keith Busch [this message]
2026-08-30 21:15 ` Sagi Grimberg
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=apCxcvW33xppjCf_@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=greg@kroah.com \
--cc=hch@lst.de \
--cc=kch@nvidia.com \
--cc=kumar.shivam43666@gmail.com \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=security@kernel.org \
--cc=stable@vger.kernel.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 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.