From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 29E2437883E; Sun, 5 Jul 2026 14:00:36 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783260038; cv=none; b=ggZUlrAj/McqlvK9KTGyEPEUgN2r6ijVLncMPQOlzRETMDuczaJTZ+FnYfsQ/bGwVA56aEvYac1dk+EiG1G1uyaAOQ7YJDz5TnEAzPP5xR8LIeqPCfbq2vdhOESqbkGityOnggxX+1EuvpZ0Rh+a1Ve6DSEHNVyEeFrOjcjNoY4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783260038; c=relaxed/simple; bh=png50S20ShN43oQFZ0KFX6+JBP2QoOZjdSEZIbE7nGc=; h=From:To:Cc:In-Reply-To:References:Subject:Message-Id:Date: MIME-Version:Content-Type; b=boGTKIul6O6bwG0oMuGOWmq0vGnqZd8EEAlBdtqyaAnrCAWN7bX4XTz0ZvOCmT1xldpcilDzuOyuXP5rNFxrB3S2/nfk2T8l9vjoEUxH31bVSnFmlJMQEuR2RVUQBMORlhJq3MZML6juOzoTbLTEp/7nZvaUXaTFhE++40rw0s4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=Gg3gPeZn; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="Gg3gPeZn" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 262AB1F000E9; Sun, 5 Jul 2026 14:00:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1783260036; bh=5uxf4qWbZxrE+bclyeo+X4WWa+BNtCzdTw3O82BRkVg=; h=From:To:Cc:In-Reply-To:References:Subject:Date; b=Gg3gPeZnv+nztE73c3L1kKLTkcDrfYYajG6/oBuEmNSbAA675tFKtLbraQxpXioYL DDrq4KywljsnuF8lvsR6ptsUlvT683TOVPDlYuWQqRfZl6leGMszYEXRYgusGVS+RT MFn4jWKS+wd+Rdww+MNy2VCCCgzqrJUVR8a/uejK7Vbi6VzL/i3SX669H0nHTkAgIN SLwmJMT+1gDytydeE1z0MnbANUTzPOhj6RR9hEkox3edHHF7OfdFCCW7eft0MJQsEU b6zjdv0lxWq7SCtcckyji1vl8w/Vo4T6aobJ4w4RU/QavZcxliKwHcxRj9Xt+7Sk86 sDgP7dJFHpmgw== From: Leon Romanovsky To: Jason Gunthorpe , Leon Romanovsky , Michael Bommarito Cc: linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org, Vlad Dumitrescu , Or Har-Toov , Bob Pearson , Sean Hefty , Kees Cook In-Reply-To: <3170ff3bc389a930bb1641f2caa394a0b2241579.1780774907.git.michael.bommarito@gmail.com> References: <3170ff3bc389a930bb1641f2caa394a0b2241579.1780774907.git.michael.bommarito@gmail.com> Subject: Re: [PATCH v3] IB/mad: drop unmatched RMPP responses before reassembly Message-Id: <178273508232.133362.14163993593921420714.b4-ty@kernel.org> Date: Mon, 29 Jun 2026 08:11:22 -0400 Precedence: bulk X-Mailing-List: linux-rdma@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Mailer: b4 0.15-dev-18f8f 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