From: patchwork-bot+netdevbpf@kernel.org
To: Wen Gu <guwen@linux.alibaba.com>
Cc: kgraul@linux.ibm.com, wenjia@linux.ibm.com, jaka@linux.ibm.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, linux-s390@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
liuyacan@corp.netease.com
Subject: Re: [PATCH net] net/smc: Reset connection when trying to use SMCRv2 fails.
Date: Fri, 19 May 2023 08:00:20 +0000 [thread overview]
Message-ID: <168448322080.32188.9310241476362959617.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1684386895-112162-1-git-send-email-guwen@linux.alibaba.com>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 18 May 2023 13:14:55 +0800 you wrote:
> We found a crash when using SMCRv2 with 2 Mellanox ConnectX-4. It
> can be reproduced by:
>
> - smc_run nginx
> - smc_run wrk -t 32 -c 500 -d 30 http://<ip>:<port>
>
> BUG: kernel NULL pointer dereference, address: 0000000000000014
> #PF: supervisor read access in kernel mode
> #PF: error_code(0x0000) - not-present page
> PGD 8000000108713067 P4D 8000000108713067 PUD 151127067 PMD 0
> Oops: 0000 [#1] PREEMPT SMP PTI
> CPU: 4 PID: 2441 Comm: kworker/4:249 Kdump: loaded Tainted: G W E 6.4.0-rc1+ #42
> Workqueue: smc_hs_wq smc_listen_work [smc]
> RIP: 0010:smc_clc_send_confirm_accept+0x284/0x580 [smc]
> RSP: 0018:ffffb8294b2d7c78 EFLAGS: 00010a06
> RAX: ffff8f1873238880 RBX: ffffb8294b2d7dc8 RCX: 0000000000000000
> RDX: 00000000000000b4 RSI: 0000000000000001 RDI: 0000000000b40c00
> RBP: ffffb8294b2d7db8 R08: ffff8f1815c5860c R09: 0000000000000000
> R10: 0000000000000400 R11: 0000000000000000 R12: ffff8f1846f56180
> R13: ffff8f1815c5860c R14: 0000000000000001 R15: 0000000000000001
> FS: 0000000000000000(0000) GS:ffff8f1aefd00000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 0000000000000014 CR3: 00000001027a0001 CR4: 00000000003706e0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> Call Trace:
> <TASK>
> ? mlx5_ib_map_mr_sg+0xa1/0xd0 [mlx5_ib]
> ? smcr_buf_map_link+0x24b/0x290 [smc]
> ? __smc_buf_create+0x4ee/0x9b0 [smc]
> smc_clc_send_accept+0x4c/0xb0 [smc]
> smc_listen_work+0x346/0x650 [smc]
> ? __schedule+0x279/0x820
> process_one_work+0x1e5/0x3f0
> worker_thread+0x4d/0x2f0
> ? __pfx_worker_thread+0x10/0x10
> kthread+0xe5/0x120
> ? __pfx_kthread+0x10/0x10
> ret_from_fork+0x2c/0x50
> </TASK>
>
> [...]
Here is the summary with links:
- [net] net/smc: Reset connection when trying to use SMCRv2 fails.
https://git.kernel.org/netdev/net/c/35112271672a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-05-19 8:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 5:14 [PATCH net] net/smc: Reset connection when trying to use SMCRv2 fails Wen Gu
2023-05-18 5:20 ` Tony Lu
2023-05-19 8:00 ` patchwork-bot+netdevbpf [this message]
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=168448322080.32188.9310241476362959617.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=guwen@linux.alibaba.com \
--cc=jaka@linux.ibm.com \
--cc=kgraul@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=liuyacan@corp.netease.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).