From: Tony Lu <tonylu@linux.alibaba.com>
To: Alexander H Duyck <alexander.duyck@gmail.com>
Cc: "D. Wythe" <alibuda@linux.alibaba.com>,
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: Wed, 8 Mar 2023 16:21:36 +0800 [thread overview]
Message-ID: <ZAhFkNd0vY784uqZ@TONYMAC-ALIBABA.local> (raw)
In-Reply-To: <a4a6c3381239d1297f218c5b6d01828bac016660.camel@gmail.com>
On Mon, Mar 06, 2023 at 08:38:52AM -0800, Alexander H Duyck wrote:
> On Mon, 2023-03-06 at 11:36 +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>
>
> Looking at the code for __smc_buf_create it seems like you might have
> more issues hiding in the code. From what I can tell smc_buf_get_slot
> can only return a pointer or NULL but it is getting checked for being
> being a PTR_ERR or IS_ERR in several spots that are likely all dead
> code.
>
> > ---
> > 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;
> > +
>
> This return value doesn't seem right to me. Rather than en EINVAL
> should this be something like a ENOBUFS just to make it easier to debug
> when this issue is encountered?
>
I agree with you. It is reasonable to use ENOBUFS here.
Thanks.
> > smc_cdc_add_pending_send(conn, pend);
> >
> > conn->tx_cdc_seq++;
>
prev parent reply other threads:[~2023-03-08 8:22 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
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 [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=ZAhFkNd0vY784uqZ@TONYMAC-ALIBABA.local \
--to=tonylu@linux.alibaba.com \
--cc=alexander.duyck@gmail.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