From: Tony Lu <tonylu@linux.alibaba.com>
To: "D. Wythe" <alibuda@linux.alibaba.com>
Cc: kgraul@linux.ibm.com, wenjia@linux.ibm.com, jaka@linux.ibm.com,
kuba@kernel.org, davem@davemloft.net, netdev@vger.kernel.org,
linux-s390@vger.kernel.org, linux-rdma@vger.kernel.org
Subject: Re: [PATCH net] net/smc: fix NULL sndbuf_desc in smc_cdc_tx_handler()
Date: Mon, 6 Mar 2023 16:40:17 +0800 [thread overview]
Message-ID: <ZAWm8YHr77t4N29F@TONYMAC-ALIBABA.local> (raw)
In-Reply-To: <1678073786-110013-1-git-send-email-alibuda@linux.alibaba.com>
On Mon, Mar 06, 2023 at 11:36:26AM +0800, D. Wythe wrote:
> From: "D. Wythe" <alibuda@linux.alibaba.com>
>
> When performing a stress test on SMC-R by rmmod mlx5_ib driver
> during the wrk/nginx test, we found that there is a probability
> of triggering a panic while terminating all link groups.
>
> This issue dues to the race between smc_smcr_terminate_all()
> and smc_buf_create().
>
> smc_smcr_terminate_all
>
> smc_buf_create
> /* init */
> conn->sndbuf_desc = NULL;
> ...
>
> __smc_lgr_terminate
> smc_conn_kill
> smc_close_abort
> smc_cdc_get_slot_and_msg_send
>
> __softirqentry_text_start
> smc_wr_tx_process_cqe
> smc_cdc_tx_handler
> READ(conn->sndbuf_desc->len);
> /* panic dues to NULL sndbuf_desc */
>
> conn->sndbuf_desc = xxx;
>
> This patch tries to fix the issue by always to check the sndbuf_desc
> before send any cdc msg, to make sure that no null pointer is
> seen during cqe processing.
>
> Fixes: 0b29ec643613 ("net/smc: immediate termination for SMCR link groups")
> Signed-off-by: D. Wythe <alibuda@linux.alibaba.com>
LGTM.
Reviewed-by: Tony Lu <tonylu@linux.alibaba.com>
> ---
> net/smc/smc_cdc.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/net/smc/smc_cdc.c b/net/smc/smc_cdc.c
> index 53f63bf..2f0e2ee 100644
> --- a/net/smc/smc_cdc.c
> +++ b/net/smc/smc_cdc.c
> @@ -114,6 +114,9 @@ int smc_cdc_msg_send(struct smc_connection *conn,
> union smc_host_cursor cfed;
> int rc;
>
> + if (unlikely(!READ_ONCE(conn->sndbuf_desc)))
> + return -EINVAL;
> +
> smc_cdc_add_pending_send(conn, pend);
>
> conn->tx_cdc_seq++;
> --
> 1.8.3.1
next prev parent reply other threads:[~2023-03-06 8:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 3:36 [PATCH net] net/smc: fix NULL sndbuf_desc in smc_cdc_tx_handler() D. Wythe
2023-03-06 8:40 ` Tony Lu [this message]
2023-03-06 16:38 ` Alexander H Duyck
2023-03-06 21:06 ` Wenjia Zhang
2023-03-07 16:27 ` Alexander H Duyck
2023-03-08 8:21 ` Tony Lu
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=ZAWm8YHr77t4N29F@TONYMAC-ALIBABA.local \
--to=tonylu@linux.alibaba.com \
--cc=alibuda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=jaka@linux.ibm.com \
--cc=kgraul@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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