public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Zhu Yanjun <yanjun.zhu@linux.dev>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Yi Zhang <yi.zhang@redhat.com>,
	RDMA mailing list <linux-rdma@vger.kernel.org>,
	Robert Pearson <rpearsonhpe@gmail.com>
Subject: Re: [bug report][bisected] rdma_rxe: blktests srp lead kernel panic with 64k page size
Date: Tue, 10 Oct 2023 21:36:57 +0800	[thread overview]
Message-ID: <d2f41bf8-45dc-4937-a3a9-b05d422499cf@linux.dev> (raw)
In-Reply-To: <20231010113542.GH3952@nvidia.com>


在 2023/10/10 19:35, Jason Gunthorpe 写道:
> On Tue, Oct 10, 2023 at 06:41:17PM +0800, Zhu Yanjun wrote:
>> 在 2023/10/9 12:35, Yi Zhang 写道:
>>> Hello
>>>
>>> blktests srp lead kernel panic[2] on aarch64 when the kernel enabled
>>> CONFIG_ARM64_64K_PAGES, bisect shows it was introduced from commit[1],
>>> pls help check it and let me know if you need any info/testing for it, thanks.
>>>
>>> [1]
>>> commit 325a7eb85199ec9c5b5a7af812f43ea16b735569
>>> Author: Bob Pearson <rpearsonhpe@gmail.com>
>>> Date:   Thu Jan 19 17:59:36 2023 -0600
>>>
>>>       RDMA/rxe: Cleanup page variables in rxe_mr.c
>>>
>>>       Cleanup usage of mr->page_shift and mr->page_mask and introduce
>>>       an extractor for mr->ibmr.page_size. Normal usage in the kernel
>>>       has page_mask masking out offset in page rather than masking out
>>>       the page number. The rxe driver had reversed that which was confusing.
>>>       Implicitly there can be a per mr page_size which was not uniformly
>>>       supported.
>>>
>>>       Link: https://lore.kernel.org/r/20230119235936.19728-6-rpearsonhpe@gmail.com
>>>       Signed-off-by: Bob Pearson <rpearsonhpe@gmail.com>
>>>       Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
>>>
>> Hi, Yi
>>
>> I delved into the commit. And the commit can not be reverted cleanly. So I
>> made the following diff to try to revert this commit. After this commit is
>> applied, rping can work well.
> We can't keep reverting things for what are probably small bugs. Fix
> the issues please!


This is not an official commit. Because the reporter mentioned that the 
commit causes this problem,

we just confirmed that. If we confirmed that this commit is the root 
cause, we will analyze this commit,

then fix it.

Zhu Yanjun


>
> Jason

  reply	other threads:[~2023-10-10 13:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-09  4:35 [bug report][bisected] rdma_rxe: blktests srp lead kernel panic with 64k page size Yi Zhang
2023-10-10  2:29 ` Zhu Yanjun
2023-10-10 10:41 ` Zhu Yanjun
2023-10-10 11:35   ` Jason Gunthorpe
2023-10-10 13:36     ` Zhu Yanjun [this message]
2023-10-11  0:33       ` Yi Zhang
2023-10-13 12:16         ` Daisuke Matsuda (Fujitsu)

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=d2f41bf8-45dc-4937-a3a9-b05d422499cf@linux.dev \
    --to=yanjun.zhu@linux.dev \
    --cc=jgg@nvidia.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=rpearsonhpe@gmail.com \
    --cc=yi.zhang@redhat.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