Prior report for the nvmet-tcp unbounded SGL length fix in 7.3

Shivam Kumar <[email protected]> Mon, 24 Aug 2026 11:42:50 -0400

Newsgroups	org.infradead.lists.linux-nvme
Message-ID	<CA+ysrSKO9ufMWQ=s_xM_uh1OhKmEb8v0tOwYH+g2vtxeWqW8DQ@mail.gmail.com>

Hi all,

I originally reported this issue to [email protected] on 2026-03-17
(Cc Sagi), Message-ID:
<CA+ysrSJUFi8cHzU8g9Nrbbkcuo0F7vh8CMn3ht15gSk3BbK45A@mail.gmail.com>
and posted the first patch for it in this thread,
"[PATCH] nvmet-tcp: bound sgl->length check in nvmet_tcp_map_data()"
(2026-03-19).

Commit 4a3f002 ("nvmet-tcp: bound SGL data length before allocating
command buffers"), merged for 7.3, adds the same NVMET_TCP_MAXH2CDATA
bound with the same status code.

These things happen independently, and I'm glad the issue is fixed.
Would it be possible to get some acknowledgement for the original
report?

Thanks,
Shivam