From: Wang Liang <wangliang74@huawei.com>
To: Kuniyuki Iwashima <kuniyu@google.com>
Cc: <alibuda@linux.alibaba.com>, <davem@davemloft.net>,
<dust.li@linux.alibaba.com>, <edumazet@google.com>,
<guwen@linux.alibaba.com>, <horms@kernel.org>, <kuba@kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-rdma@vger.kernel.org>,
<linux-s390@vger.kernel.org>, <mjambigi@linux.ibm.com>,
<netdev@vger.kernel.org>, <pabeni@redhat.com>,
<sidraya@linux.ibm.com>, <tonylu@linux.alibaba.com>,
<wenjia@linux.ibm.com>, <yuehaibing@huawei.com>,
<zhangchangzhong@huawei.com>
Subject: Re: [PATCH net v2] net/smc: fix general protection fault in __smc_diag_dump
Date: Fri, 17 Oct 2025 15:45:41 +0800 [thread overview]
Message-ID: <ecd158c4-5af7-415c-9d29-d5ec8fec49a2@huawei.com> (raw)
In-Reply-To: <20251017055106.3603987-1-kuniyu@google.com>
在 2025/10/17 13:48, Kuniyuki Iwashima 写道:
> From: Wang Liang <wangliang74@huawei.com>
> Date: Fri, 17 Oct 2025 10:48:27 +0800
>> The syzbot report a crash:
>>
>> Oops: general protection fault, probably for non-canonical address 0xfbd5a5d5a0000003: 0000 [#1] SMP KASAN NOPTI
>> KASAN: maybe wild-memory-access in range [0xdead4ead00000018-0xdead4ead0000001f]
>> CPU: 1 UID: 0 PID: 6949 Comm: syz.0.335 Not tainted syzkaller #0 PREEMPT(full)
>> Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
>> RIP: 0010:smc_diag_msg_common_fill net/smc/smc_diag.c:44 [inline]
>> RIP: 0010:__smc_diag_dump.constprop.0+0x3ca/0x2550 net/smc/smc_diag.c:89
>> Call Trace:
>> <TASK>
>> smc_diag_dump_proto+0x26d/0x420 net/smc/smc_diag.c:217
>> smc_diag_dump+0x27/0x90 net/smc/smc_diag.c:234
>> netlink_dump+0x539/0xd30 net/netlink/af_netlink.c:2327
>> __netlink_dump_start+0x6d6/0x990 net/netlink/af_netlink.c:2442
>> netlink_dump_start include/linux/netlink.h:341 [inline]
>> smc_diag_handler_dump+0x1f9/0x240 net/smc/smc_diag.c:251
>> __sock_diag_cmd net/core/sock_diag.c:249 [inline]
>> sock_diag_rcv_msg+0x438/0x790 net/core/sock_diag.c:285
>> netlink_rcv_skb+0x158/0x420 net/netlink/af_netlink.c:2552
>> netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline]
>> netlink_unicast+0x5a7/0x870 net/netlink/af_netlink.c:1346
>> netlink_sendmsg+0x8d1/0xdd0 net/netlink/af_netlink.c:1896
>> sock_sendmsg_nosec net/socket.c:714 [inline]
>> __sock_sendmsg net/socket.c:729 [inline]
>> ____sys_sendmsg+0xa95/0xc70 net/socket.c:2614
>> ___sys_sendmsg+0x134/0x1d0 net/socket.c:2668
>> __sys_sendmsg+0x16d/0x220 net/socket.c:2700
>> do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
>> do_syscall_64+0xcd/0x4e0 arch/x86/entry/syscall_64.c:94
>> entry_SYSCALL_64_after_hwframe+0x77/0x7f
>> </TASK>
>>
>> The process like this:
>>
>> (CPU1) | (CPU2)
>> ---------------------------------|-------------------------------
>> inet_create() |
>> // init clcsock to NULL |
>> sk = sk_alloc() |
>> |
>> // unexpectedly change clcsock |
>> inet_init_csk_locks() |
>> |
>> // add sk to hash table |
>> smc_inet_init_sock() |
>> smc_sk_init() |
>> smc_hash_sk() |
>> | // traverse the hash table
>> | smc_diag_dump_proto
>> | __smc_diag_dump()
>> | // visit wrong clcsock
>> | smc_diag_msg_common_fill()
>> // alloc clcsock |
>> smc_create_clcsk |
>> sock_create_kern |
>>
>> With CONFIG_DEBUG_LOCK_ALLOC=y, the smc->clcsock is unexpectedly changed
>> in inet_init_csk_locks(). The INET_PROTOSW_ICSK flag is no need by smc,
>> just remove it.
>>
>> After removing the INET_PROTOSW_ICSK flag, this patch alse revert
>> commit 6fd27ea183c2 ("net/smc: fix lacks of icsk_syn_mss with IPPROTO_SMC")
>> to avoid casting smc_sock to inet_connection_sock.
>>
>> Reported-by: syzbot+f775be4458668f7d220e@syzkaller.appspotmail.com
>> Closes: https://syzkaller.appspot.com/bug?extid=f775be4458668f7d220e
>> Tested-by: syzbot+f775be4458668f7d220e@syzkaller.appspotmail.com
> nit: looks like this diff is not tested by syzbot, you may
> want to send diff to syzbot.
>
Thank you for the reminder!
I just sent this diff to syzbot, and the test return OK:
https://lore.kernel.org/netdev/b76f348d-61d3-404b-81c6-57621a14046b@huawei.com/T/#t
------
Best regards
Wang Liang
>> Fixes: d25a92ccae6b ("net/smc: Introduce IPPROTO_SMC")
>> Signed-off-by: Wang Liang <wangliang74@huawei.com>
> Change itself looks good.
>
> Reviewed-by: Kuniyuki Iwashima <kuniyu@google.com>
>
> Thanks!
next prev parent reply other threads:[~2025-10-17 7:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 2:48 [PATCH net v2] net/smc: fix general protection fault in __smc_diag_dump Wang Liang
2025-10-17 5:48 ` Kuniyuki Iwashima
2025-10-17 5:54 ` Eric Dumazet
2025-10-17 7:45 ` Wang Liang [this message]
2025-10-17 9:03 ` D. Wythe
2025-10-21 0:50 ` patchwork-bot+netdevbpf
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=ecd158c4-5af7-415c-9d29-d5ec8fec49a2@huawei.com \
--to=wangliang74@huawei.com \
--cc=alibuda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=dust.li@linux.alibaba.com \
--cc=edumazet@google.com \
--cc=guwen@linux.alibaba.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--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 \
--cc=yuehaibing@huawei.com \
--cc=zhangchangzhong@huawei.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