Re: [PATCH v2] RDMA/rxe: Generate async error for r_key violations

[Leon Romanovsky]

On Fri, 20 Feb 2026 10:55:04 -0800, Evan Green wrote:
> Table 63 of the IBTA spec lists R_Key violations as a class C
> error. 9.9.3.1.3 Responder Class C Fault Behavior indicates an
> affiliated asynchronous error should be generated at the responder
> if the error can be associated to a QP but not a particular RX WQE.
> 
> Relevant portion of the spec:
> C9-222.1.1: For an HCA responder using Reliable Connection service, for
> a Class C responder side error, the error shall be reported to the
> requester by generating the appropriate NAK code as specified in Table 63
> Responder Error Behavior Summary on page 448. If the error can be related
> to a particular QP but cannot be related to a particular WQE on that
> receive queue (e.g. the error occurred while executing an RDMA Write
> Request without immediate data), the error shall be reported to the
> responder’s client as an Affiliated Asynchronous error. See Section
> 10.10.2.3 Asynchronous Errors on page 576 for details. If the error can be
> related to a particular WQE on a given receive queue, the QP shall be
> placed into the error state and the error shall be reported to the
> responder’s client as a Completion error.
> 
> [...]

Applied, thanks!

[1/1] RDMA/rxe: Generate async error for r_key violations
      https://git.kernel.org/rdma/rdma/c/f3f9825837dfdc

Best regards,
-- 
Leon Romanovsky <leon@xxxxxxxxxx>