From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>,
Michael Bommarito <michael.bommarito@gmail.com>
Cc: linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, Vlad Dumitrescu <vdumitrescu@nvidia.com>,
Or Har-Toov <ohartoov@nvidia.com>,
Bob Pearson <rpearsonhpe@gmail.com>,
Sean Hefty <shefty@nvidia.com>, Kees Cook <kees@kernel.org>
Subject: Re: [PATCH v3] IB/mad: drop unmatched RMPP responses before reassembly
Date: Mon, 29 Jun 2026 08:11:22 -0400 [thread overview]
Message-ID: <178273508232.133362.14163993593921420714.b4-ty@kernel.org> (raw)
In-Reply-To: <3170ff3bc389a930bb1641f2caa394a0b2241579.1780774907.git.michael.bommarito@gmail.com>
On Sat, 06 Jun 2026 16:01:55 -0400, Michael Bommarito wrote:
> Kernel-handled RMPP receive processing starts reassembly for active
> DATA responses before the response is matched to an outstanding send.
> The normal match happens later, after ib_process_rmpp_recv_wc() has
> either assembled a complete message or consumed the segment.
>
> That ordering lets an unsolicited response that routes to a kernel
> RMPP agent by the high TID bits allocate or extend RMPP receive state
> before the full TID and source address are checked against a real
> request. A reordered burst can therefore reach the receive-side
> insertion path even though the response would not match any send.
>
> [...]
Applied, thanks!
[1/1] IB/mad: drop unmatched RMPP responses before reassembly
https://git.kernel.org/rdma/rdma/c/d2e52d610b9b09
Best regards,
--
Leon Romanovsky <leon@kernel.org>
prev parent reply other threads:[~2026-07-05 14:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 21:23 [PATCH] IB/mad: cap RMPP reassembly window size to bound find_seg_location walk Michael Bommarito
2026-05-19 14:46 ` Leon Romanovsky
2026-05-20 15:47 ` [PATCH v2] IB/mad: cap RMPP reassembly window size Michael Bommarito
2026-06-03 17:54 ` Jason Gunthorpe
2026-06-03 18:20 ` Michael Bommarito
2026-06-03 18:41 ` Jason Gunthorpe
2026-06-06 20:01 ` [PATCH v3] IB/mad: drop unmatched RMPP responses before reassembly Michael Bommarito
2026-06-29 12:11 ` Leon Romanovsky [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=178273508232.133362.14163993593921420714.b4-ty@kernel.org \
--to=leon@kernel.org \
--cc=jgg@ziepe.ca \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=michael.bommarito@gmail.com \
--cc=ohartoov@nvidia.com \
--cc=rpearsonhpe@gmail.com \
--cc=shefty@nvidia.com \
--cc=stable@vger.kernel.org \
--cc=vdumitrescu@nvidia.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®