From: Yuval Shaia <yuval.shaia@oracle.com>
To: Bart Van Assche <bart.vanassche@wdc.com>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
Doug Ledford <dledford@redhat.com>,
linux-rdma@vger.kernel.org, Zhu Yanjun <yanjun.zhu@oracle.com>,
Jianchao Wang <jianchao.w.wang@oracle.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v2] RDMA/rxe: Set wqe->status correctly if an unexpected response is received
Date: Wed, 27 Jun 2018 19:31:50 +0300 [thread overview]
Message-ID: <20180627163150.GA9553@lap1> (raw)
In-Reply-To: <20180626153936.9576-1-bart.vanassche@wdc.com>
On Tue, Jun 26, 2018 at 08:39:36AM -0700, Bart Van Assche wrote:
> Every function that returns COMPST_ERROR must set wqe->status to
> another value than IB_WC_SUCCESS before returning COMPST_ERROR. Fix
> the only code path for which this is not yet the case.
It is unclear to me why other places left out from this fix (e.x. lines
248, 288 etc).
>
> Signed-off-by: Bart Van Assche <bart.vanassche@wdc.com>
> Cc: Zhu Yanjun <yanjun.zhu@oracle.com>
> Cc: Jianchao Wang <jianchao.w.wang@oracle.com>
> Cc: Yuval Shaia <yuval.shaia@oracle.com>
> Cc: <stable@vger.kernel.org>
> ---
>
> Changes compared to v1: left out a pr_err() statement as requested by Jason.
>
> drivers/infiniband/sw/rxe/rxe_comp.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/infiniband/sw/rxe/rxe_comp.c b/drivers/infiniband/sw/rxe/rxe_comp.c
> index 98d470d1f3fc..83311dd07019 100644
> --- a/drivers/infiniband/sw/rxe/rxe_comp.c
> +++ b/drivers/infiniband/sw/rxe/rxe_comp.c
> @@ -276,6 +276,7 @@ static inline enum comp_state check_ack(struct rxe_qp *qp,
> case IB_OPCODE_RC_RDMA_READ_RESPONSE_MIDDLE:
> if (wqe->wr.opcode != IB_WR_RDMA_READ &&
> wqe->wr.opcode != IB_WR_RDMA_READ_WITH_INV) {
> + wqe->status = IB_WC_FATAL_ERR;
> return COMPST_ERROR;
> }
> reset_retry_counters(qp);
> --
> 2.17.1
>
next prev parent reply other threads:[~2018-06-27 16:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 15:39 [PATCH v2] RDMA/rxe: Set wqe->status correctly if an unexpected response is received Bart Van Assche
2018-06-27 16:31 ` Yuval Shaia [this message]
2018-06-27 16:41 ` Bart Van Assche
2018-06-28 8:58 ` Moni Shoua
2018-06-28 15:47 ` Bart Van Assche
2018-08-08 15:58 ` Jason Gunthorpe
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=20180627163150.GA9553@lap1 \
--to=yuval.shaia@oracle.com \
--cc=bart.vanassche@wdc.com \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=jianchao.w.wang@oracle.com \
--cc=linux-rdma@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=yanjun.zhu@oracle.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;
as well as URLs for NNTP newsgroup(s).