All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yanjun Zhu <yanjun.zhu@linux.dev>
To: "yangx.jy@fujitsu.com" <yangx.jy@fujitsu.com>,
	Zhu Yanjun <zyjzyj2000@gmail.com>,
	Bob Pearson <rpearsonhpe@gmail.com>
Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: null pointer in rxe_mr_copy()
Date: Wed, 25 May 2022 07:56:21 +0800	[thread overview]
Message-ID: <10df6324-0c48-5902-3a7c-7cd898cd561d@linux.dev> (raw)
In-Reply-To: <84888208-ac2e-115c-43d5-2ef211948c78@fujitsu.com>

在 2022/5/24 21:18, yangx.jy@fujitsu.com 写道:
> On 2022/4/11 13:34, Zhu Yanjun wrote:
>>    738         if (res->state == rdatm_res_state_new) {
>>    739                 mr = qp->resp.mr;
>> <----It seems that mr is from here.
>>    740                 qp->resp.mr = NULL;
>>    741
> 
> Hi Bob and Yanjun
> 
> I wonder if the following patch has fixed the null pointer issue in
> rxe_mr_copy().

Yes.

Zhu Yanjun

> 
> commit 570a4bf7440e9fb2a4164244a6bf60a46362b627
> Author: Bob Pearson <rpearsonhpe@gmail.com>
> Date:   Mon Apr 18 12:41:04 2022 -0500
> 
>       RDMA/rxe: Recheck the MR in when generating a READ reply
> 
> Best Regards,
> Xiao Yang


  parent reply	other threads:[~2022-05-24 23:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11  3:34 null pointer in rxe_mr_copy() Bob Pearson
2022-04-11  5:14 ` Zhu Yanjun
2022-04-11  5:34   ` Zhu Yanjun
2022-04-11 16:25     ` Pearson, Robert B
2022-04-12  3:13       ` Bob Pearson
2022-04-12 10:04         ` Yanjun Zhu
2022-05-24 13:18     ` yangx.jy
2022-05-24 18:07       ` Bob Pearson
2022-05-24 23:56       ` Yanjun Zhu [this message]
2022-04-12  4:11 ` Bob Pearson

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=10df6324-0c48-5902-3a7c-7cd898cd561d@linux.dev \
    --to=yanjun.zhu@linux.dev \
    --cc=linux-rdma@vger.kernel.org \
    --cc=rpearsonhpe@gmail.com \
    --cc=yangx.jy@fujitsu.com \
    --cc=zyjzyj2000@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.