From: Leon Romanovsky <leon@kernel.org>
To: "yangx.jy@fujitsu.com" <yangx.jy@fujitsu.com>
Cc: "jgg@nvidia.com" <jgg@nvidia.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH v3] RDMA/rxe: Generate a completion on error after getting a wqe
Date: Fri, 1 Apr 2022 07:50:50 +0300 [thread overview]
Message-ID: <YkaEqgP3254QLRuS@unreal> (raw)
In-Reply-To: <8b90851c-72ba-1eb2-7e94-ee7d6a178fc7@fujitsu.com>
On Fri, Apr 01, 2022 at 03:52:37AM +0000, yangx.jy@fujitsu.com wrote:
> On 2022/4/1 1:19, Leon Romanovsky wrote:
>
> ret = finish_packet(qp, av, wqe, &pkt, skb, payload);
> if (unlikely(ret)) {
> pr_debug("qp#%d Error during finish packet\n", qp_num(qp));
> + if (ah)
>
>
> No, ah can't be NULL. This is why I proposed to clean rxe_get_av() too.
> **ahp is not NULL, as an input to that function and in all flows it is
> updated with new ah pointer. If it can't update, the NULL will be
> returned and rxe_requester() will exit.
Please use plain-text friendly email client.
>
> Hi Leon,
>
> If ah_num is 0 in rxe_get_av(), rxe_get_av() returns not NULL (i.e. av is not NULL) and ah is NULL.
> In this case, I think we can reach here and ah is NULL.
> BTW, I don't want to mix the fix and the change of rxe_get_av()'s logic.
ok, no problem.
Thanks
>
> Best Regards,
>
> Xiao Yang
next prev parent reply other threads:[~2022-04-01 4:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 12:02 [PATCH v3] RDMA/rxe: Generate a completion on error after getting a wqe Xiao Yang
2022-03-31 17:19 ` Leon Romanovsky
[not found] ` <8b90851c-72ba-1eb2-7e94-ee7d6a178fc7@fujitsu.com>
2022-04-01 4:50 ` Leon Romanovsky [this message]
2022-04-01 5:09 ` yangx.jy
2022-04-07 21:39 ` Bob Pearson
2022-04-08 3:14 ` 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=YkaEqgP3254QLRuS@unreal \
--to=leon@kernel.org \
--cc=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=yangx.jy@fujitsu.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