From: Zhu Yanjun <yanjun.zhu@linux.dev>
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: Bernard Metzler <BMT@zurich.ibm.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Daniel Wagner <wagi@kernel.org>
Subject: Re: [bug report] blktests nvme/061 hang with rdma transport and siw driver
Date: Wed, 16 Apr 2025 07:14:18 +0200 [thread overview]
Message-ID: <f5eaa6c4-3676-4da3-ae47-759b9a0f357d@linux.dev> (raw)
In-Reply-To: <mrdhqtchtzw5f7ypno6d5g4fwh7heoyx5nyjvfak46cneprdrm@o4q2olnuq4gg>
在 2025/4/16 4:50, Shinichiro Kawasaki 写道:
> On Apr 15, 2025 / 17:00, Zhu Yanjun wrote:
>> On 15.04.25 15:09, Bernard Metzler wrote:
>>
>>> [ 106.826346] rdma_rxe: loaded
>>> [ 106.832164] loop: module loaded
>>> [ 107.066868] run blktests nvme/061 at 2025-04-15 15:03:04
>>> [ 107.081270] infiniband eno1_rxe: set active
>>> [ 107.081274] infiniband eno1_rxe: added eno1
>>> [ 107.089683] infiniband enp4s0f4d1_rxe: set active
>>> [ 107.089687] infiniband enp4s0f4d1_rxe: added enp4s0f4d1
>>> [ 107.264770] loop0: detected capacity change from 0 to 2097152
>>> [ 107.267376] nvmet: adding nsid 1 to subsystem blktests-subsystem-1
>>> [ 107.271276] nvmet_rdma: enabling port 0 (10.0.0.2:4420)
>>> [ 107.312957] BUG: kernel NULL pointer dereference, address: 0000000000000028
>>> [ 107.312973] #PF: supervisor read access in kernel mode
>>> [ 107.312979] #PF: error_code(0x0000) - not-present page
>>> [ 107.312986] PGD 0 P4D 0
>>> [ 107.312992] Oops: Oops: 0000 [#1] SMP PTI
>>> [ 107.312999] CPU: 1 UID: 0 PID: 123 Comm: kworker/u32:4 Not tainted 6.15.0-rc2 #1 PREEMPT(undef)
>>> [ 107.313008] Hardware name: LENOVO 10A6S05601/SHARKBAY, BIOS FBKTD8AUS 09/17/2019
>>> [ 107.313016] Workqueue: rxe_wq do_work [rdma_rxe]
>>> [ 107.313030] RIP: 0010:rxe_mr_copy+0x58/0x230 [rdma_rxe]
>>
>> Hi, Bernard
>>
>> An interesting test. Can you find the line number of
>> (rxe_mr_copy+0x58/0x230) with crash tool?
>>
>> Thus we can find what variable is becoming NULL pointer.
>
> I observe the failure too, but I also observe the recent patch [1] avoids it.
> With the patch applied to the kernel v6.15-rc2, I no longer observe the failure
> repeating the test case 100 times using rxe driver.
>
> [1] https://lore.kernel.org/linux-rdma/20250402032657.1762800-1-lizhijian@fujitsu.com/
Hi, Shinichiro
Your confirmation is important for us.
Thanks a lot. I am very glad that the above commit can fix the
aforementioned problem.
Best Regards,
Zhu Yanjun
next prev parent reply other threads:[~2025-04-16 5:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 11:13 [bug report] blktests nvme/061 hang with rdma transport and siw driver Shinichiro Kawasaki
2025-04-15 13:09 ` Bernard Metzler
2025-04-15 15:00 ` Zhu Yanjun
2025-04-16 2:50 ` Shinichiro Kawasaki
2025-04-16 5:14 ` Zhu Yanjun [this message]
2025-04-15 15:18 ` Bernard Metzler
2025-04-16 3:42 ` Shinichiro Kawasaki
2025-05-08 7:03 ` Shinichiro Kawasaki
2025-05-08 12:25 ` Jason Gunthorpe
2025-05-08 14:23 ` Bernard Metzler
2025-05-09 9:03 ` Shinichiro Kawasaki
2025-05-08 14:22 ` Bernard Metzler
2025-05-09 10:21 ` Zhu Yanjun
2025-05-10 9:59 ` Shinichiro Kawasaki
2025-05-10 10:04 ` Shinichiro Kawasaki
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=f5eaa6c4-3676-4da3-ae47-759b9a0f357d@linux.dev \
--to=yanjun.zhu@linux.dev \
--cc=BMT@zurich.ibm.com \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-rdma@vger.kernel.org \
--cc=shinichiro.kawasaki@wdc.com \
--cc=wagi@kernel.org \
/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