From: Leon Romanovsky <leonro@nvidia.com>
To: Xiao Yang <yangx.jy@fujitsu.com>
Cc: <linux-rdma@vger.kernel.org>, <jgg@nvidia.com>,
<rpearsonhpe@gmail.com>, <yanjun.zhu@linux.dev>
Subject: Re: [PATCH] RDMA/rxe: Generate a completion on error after getting a wqe
Date: Mon, 28 Mar 2022 14:27:24 +0300 [thread overview]
Message-ID: <YkGbnOEe8GBhjNqN@unreal> (raw)
In-Reply-To: <20220328095436.304063-1-yangx.jy@fujitsu.com>
On Mon, Mar 28, 2022 at 05:54:36PM +0800, Xiao Yang wrote:
> Current rxe_requester() doesn't generate a completion on error after
> getting a wqe. Fix the issue by calling "goto err;" instead.
>
> Signed-off-by: Xiao Yang <yangx.jy@fujitsu.com>
> ---
> drivers/infiniband/sw/rxe/rxe_req.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
Don't you need to set wqe->status too to have complete fix?
Thanks
>
> diff --git a/drivers/infiniband/sw/rxe/rxe_req.c b/drivers/infiniband/sw/rxe/rxe_req.c
> index ae5fbc79dd5c..6f8dd2b3b817 100644
> --- a/drivers/infiniband/sw/rxe/rxe_req.c
> +++ b/drivers/infiniband/sw/rxe/rxe_req.c
> @@ -648,26 +648,26 @@ int rxe_requester(void *arg)
> psn_compare(qp->req.psn, (qp->comp.psn +
> RXE_MAX_UNACKED_PSNS)) > 0)) {
> qp->req.wait_psn = 1;
> - goto exit;
> + goto err;
> }
>
> /* Limit the number of inflight SKBs per QP */
> if (unlikely(atomic_read(&qp->skb_out) >
> RXE_INFLIGHT_SKBS_PER_QP_HIGH)) {
> qp->need_req_skb = 1;
> - goto exit;
> + goto err;
> }
>
> opcode = next_opcode(qp, wqe, wqe->wr.opcode);
> if (unlikely(opcode < 0)) {
> wqe->status = IB_WC_LOC_QP_OP_ERR;
> - goto exit;
> + goto err;
> }
>
> mask = rxe_opcode[opcode].mask;
> if (unlikely(mask & RXE_READ_OR_ATOMIC_MASK)) {
> if (check_init_depth(qp, wqe))
> - goto exit;
> + goto err;
> }
>
> mtu = get_mtu(qp);
> --
> 2.23.0
>
>
>
next prev parent reply other threads:[~2022-03-28 11:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 9:54 [PATCH] RDMA/rxe: Generate a completion on error after getting a wqe Xiao Yang
2022-03-28 11:27 ` Leon Romanovsky [this message]
2022-03-28 15:12 ` yangx.jy
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=YkGbnOEe8GBhjNqN@unreal \
--to=leonro@nvidia.com \
--cc=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=rpearsonhpe@gmail.com \
--cc=yangx.jy@fujitsu.com \
--cc=yanjun.zhu@linux.dev \
/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).