From: Keith Busch <kbusch@kernel.org>
To: bestswngs@gmail.com
Cc: hch@lst.de, sagi@grimberg.me, kch@nvidia.com,
linux-nvme@lists.infradead.org, xmei5@asu.edu,
stable@vger.kernel.org, co+e015e82956da641b@bugs.sh
Subject: Re: [PATCH nvme] nvmet-rdma: reject short connection requests
Date: Wed, 28 Oct 2026 09:37:04 -0600 [thread overview]
Message-ID: <auIWoGsLbOAXPekV@kbusch-mbp> (raw)
In-Reply-To: <20261016172336.286341-3-bestswngs@gmail.com>
On Fri, Oct 16, 2026 at 10:23:38AM -0700, bestswngs@gmail.com wrote:
> From: Weiming Shi <bestswngs@gmail.com>
>
> nvmet_rdma_parse_cm_connect_req() treats RDMA-CM private data as a
> struct nvme_rdma_cm_req but accepts any nonzero private_data_len. The
> iWARP path allocates exactly the peer-provided length, so a six-byte MPA
> request reaches the parser and the hsqsize load reads two bytes past the
> allocation.
Thanks, applied to nvme-7.4.
The sashiko complaint does not look related to this patch and can be
addressed separately.
prev parent reply other threads:[~2026-10-28 15:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 17:23 [PATCH nvme] nvmet-rdma: reject short connection requests bestswngs
2026-10-16 17:35 ` sashiko-bot
2026-10-28 14:50 ` Christoph Hellwig
2026-10-28 15:37 ` 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=auIWoGsLbOAXPekV@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=bestswngs@gmail.com \
--cc=co+e015e82956da641b@bugs.sh \
--cc=hch@lst.de \
--cc=kch@nvidia.com \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=stable@vger.kernel.org \
--cc=xmei5@asu.edu \
/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.