IB/rxe: Don't update the response PSN unless it's going forwards

A client might post a read followed by a send. The partner receives
and acknowledges both transactions, posting an RCQ entry for the
send, but something goes wrong with the read ACK. When the client
retries the read, the partner's responder processes the duplicate
read but incorrectly resets the PSN to the value preceding the
original send. When the duplicate send arrives, the responder cannot
tell that it is a duplicate, so the responder generates a duplicate
RCQ entry, confusing the client.

Signed-off-by: Andrew Boyer <andrew.boyer@dell.com>
Reviewed-by: Yonatan Cohen <yonatanc@mellanox.com>
Signed-off-by: Doug Ledford <dledford@redhat.com>

diff --git a/drivers/infiniband/sw/rxe/rxe_resp.c b/drivers/infiniband/sw/rxe/rxe_resp.c
index dd3d88adc003086de0c5ef5520de0a92e9b34c09..cb3fd4cb0daa6790ee7b336729cce13ec7fd2da0 100644 (file)
--- a/drivers/infiniband/sw/rxe/rxe_resp.c
+++ b/drivers/infiniband/sw/rxe/rxe_resp.c
@@ -742,7 +742,8 @@ static enum resp_states read_reply(struct rxe_qp *qp,
        } else {
                qp->resp.res = NULL;
                qp->resp.opcode = -1;
-               qp->resp.psn = res->cur_psn;
+               if (psn_compare(res->cur_psn, qp->resp.psn) >= 0)
+                       qp->resp.psn = res->cur_psn;
                state = RESPST_CLEANUP;
        }