From: "yanjun.zhu" <yanjun.zhu@linux.dev>
To: Liu Jian <liujian56@huawei.com>,
alibuda@linux.alibaba.com, dust.li@linux.alibaba.com,
sidraya@linux.ibm.com, wenjia@linux.ibm.com,
mjambigi@linux.ibm.com, tonylu@linux.alibaba.com,
guwen@linux.alibaba.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, guangguan.wang@linux.alibaba.com
Cc: linux-rdma@vger.kernel.org, linux-s390@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH net v2] net/smc: fix one NULL pointer dereference in smc_ib_is_sg_need_sync()
Date: Thu, 28 Aug 2025 11:24:43 -0700 [thread overview]
Message-ID: <2a18ff00-e11e-433a-9aff-0bf080c4d7a4@linux.dev> (raw)
In-Reply-To: <20250828124117.2622624-1-liujian56@huawei.com>
On 8/28/25 5:41 AM, Liu Jian wrote:
> BUG: kernel NULL pointer dereference, address: 00000000000002ec
> PGD 0 P4D 0
> Oops: Oops: 0000 [#1] SMP PTI
> CPU: 28 UID: 0 PID: 343 Comm: kworker/28:1 Kdump: loaded Tainted: G OE 6.17.0-rc2+ #9 NONE
> Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014
> Workqueue: smc_hs_wq smc_listen_work [smc]
> RIP: 0010:smc_ib_is_sg_need_sync+0x9e/0xd0 [smc]
> ...
> Call Trace:
> <TASK>
> smcr_buf_map_link+0x211/0x2a0 [smc]
> __smc_buf_create+0x522/0x970 [smc]
> smc_buf_create+0x3a/0x110 [smc]
> smc_find_rdma_v2_device_serv+0x18f/0x240 [smc]
> ? smc_vlan_by_tcpsk+0x7e/0xe0 [smc]
> smc_listen_find_device+0x1dd/0x2b0 [smc]
> smc_listen_work+0x30f/0x580 [smc]
> process_one_work+0x18c/0x340
> worker_thread+0x242/0x360
> kthread+0xe7/0x220
> ret_from_fork+0x13a/0x160
> ret_from_fork_asm+0x1a/0x30
> </TASK>
>
> If the software RoCE device is used, ibdev->dma_device is a null pointer.
> As a result, the problem occurs. Null pointer detection is added to
> prevent problems.
Normally, SoftRoCE relies on the DMA capabilities of the underlying NIC
device. In SMC, if DMA will play an important role in the subsequent
operations, we can leverage the NIC device’s DMA.
If DMA is not required for the upcoming actions, then this kind of
checking is sufficient.
Reviewed-by: Zhu Yanjun <yanjun.zhu@linux.dev>
Zhu Yanjun
>
> Fixes: 0ef69e788411c ("net/smc: optimize for smc_sndbuf_sync_sg_for_device and smc_rmb_sync_sg_for_cpu")
> Signed-off-by: Liu Jian <liujian56@huawei.com>
> ---
> v1->v2:
> move the check outside of loop.
> net/smc/smc_ib.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/net/smc/smc_ib.c b/net/smc/smc_ib.c
> index 53828833a3f7..a42ef3f77b96 100644
> --- a/net/smc/smc_ib.c
> +++ b/net/smc/smc_ib.c
> @@ -742,6 +742,9 @@ bool smc_ib_is_sg_need_sync(struct smc_link *lnk,
> unsigned int i;
> bool ret = false;
>
> + if (!lnk->smcibdev->ibdev->dma_device)
> + return ret;
> +
> /* for now there is just one DMA address */
> for_each_sg(buf_slot->sgt[lnk->link_idx].sgl, sg,
> buf_slot->sgt[lnk->link_idx].nents, i) {
next prev parent reply other threads:[~2025-08-28 18:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 12:41 [PATCH net v2] net/smc: fix one NULL pointer dereference in smc_ib_is_sg_need_sync() Liu Jian
2025-08-28 13:04 ` Guangguan Wang
2025-08-28 18:24 ` yanjun.zhu [this message]
2025-08-29 3:32 ` D. Wythe
2025-09-02 9:20 ` patchwork-bot+netdevbpf
2025-09-09 9:45 ` Leon Romanovsky
2026-01-26 4:45 ` D. Wythe
2026-01-27 12:00 ` Leon Romanovsky
2026-01-28 5:50 ` D. Wythe
2026-01-28 11:21 ` Leon Romanovsky
2026-01-28 12:50 ` D. Wythe
2026-01-30 9:18 ` D. Wythe
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=2a18ff00-e11e-433a-9aff-0bf080c4d7a4@linux.dev \
--to=yanjun.zhu@linux.dev \
--cc=alibuda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=dust.li@linux.alibaba.com \
--cc=edumazet@google.com \
--cc=guangguan.wang@linux.alibaba.com \
--cc=guwen@linux.alibaba.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=liujian56@huawei.com \
--cc=mjambigi@linux.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sidraya@linux.ibm.com \
--cc=tonylu@linux.alibaba.com \
--cc=wenjia@linux.ibm.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