From: "Pearson, Robert B" <robert.pearson2@hpe.com>
To: "yangx.jy@fujitsu.com" <yangx.jy@fujitsu.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
Bob Pearson <rpearsonhpe@gmail.com>
Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"leon@kernel.org" <leon@kernel.org>,
"zyjzyj2000@gmail.com" <zyjzyj2000@gmail.com>
Subject: RE: [PATCH] RDMA/rxe: Process received packets in time
Date: Fri, 8 Jul 2022 07:46:10 +0000 [thread overview]
Message-ID: <MW4PR84MB2307B1FC7BB7FE0EDDF3BE2DBC829@MW4PR84MB2307.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <416a459a-2b27-7538-294c-1f2362a2eb2f@fujitsu.com>
I am on vacation until July 12. I will be happy to review these when I get back.
Bob
-----Original Message-----
From: yangx.jy@fujitsu.com <yangx.jy@fujitsu.com>
Sent: Friday, July 8, 2022 1:34 AM
To: Jason Gunthorpe <jgg@ziepe.ca>; Bob Pearson <rpearsonhpe@gmail.com>
Cc: linux-rdma@vger.kernel.org; leon@kernel.org; zyjzyj2000@gmail.com
Subject: Re: [PATCH] RDMA/rxe: Process received packets in time
On 2022/7/4 22:23, yangx.jy@fujitsu.com wrote:
> On 2022/7/4 20:55, Jason Gunthorpe wrote:
>> On Sun, Jul 03, 2022 at 11:56:25PM +0800, Xiao Yang wrote:
>>> If received packets (i.e. skb) stored in qp->resp_pkts cannot be
>>> processed in time, they may be ovewritten/reused and then lead to
>>> abnormal behavior.
>>
>> I just merged a bunch of fixed from Bob on atomics, do they solve
>> this problem too by chance?
> Hi Jason,
>
> Do you mean that I should use RDMA for-next branch to confirm the issue?
>
> I don't think Bob's patches can solve this problem by chance, but I
> will use RDMA for-next branch to test the issue on my slow vm.
Hi Jason,
I confirmed that the following patch avoided this issue on my slow vm.
commit dc1848388137d20e5786b976caa49a26889f36f3
Author: Bob Pearson <rpearsonhpe@gmail.com>
Date: Mon Jun 6 09:38:37 2022 -0500
RDMA/rxe: Merge normal and retry atomic flows
I think this issue is related to res->atomic.skb which has been removed by the patch. However I am still confused about why res->atomic.skb will be overwritten/reused as my commit message described.
Best Regards,
Xiao Yang
>
> Best Regards,
> Xiao Yang
>>
>> Jason
next prev parent reply other threads:[~2022-07-08 7:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 15:56 [PATCH] RDMA/rxe: Process received packets in time Xiao Yang
2022-07-04 12:55 ` Jason Gunthorpe
2022-07-04 14:23 ` yangx.jy
2022-07-08 6:33 ` yangx.jy
2022-07-08 7:46 ` Pearson, Robert B [this message]
2022-07-05 3:43 ` Li, Zhijian
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=MW4PR84MB2307B1FC7BB7FE0EDDF3BE2DBC829@MW4PR84MB2307.NAMPRD84.PROD.OUTLOOK.COM \
--to=robert.pearson2@hpe.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox