From: Simon Horman <simon.horman@corigine.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 fallback failed while sendmsg with fastopen
Date: Mon, 6 Mar 2023 13:24:49 +0100 [thread overview]
Message-ID: <ZAXbkUh4h2rIJdR2@corigine.com> (raw)
In-Reply-To: <1678075728-18812-1-git-send-email-alibuda@linux.alibaba.com>
On Mon, Mar 06, 2023 at 12:08:48PM +0800, D. Wythe wrote:
> From: "D. Wythe" <alibuda@linux.alibaba.com>
>
> Before determining whether the msg has unsupported options, it has been
> prematurely terminated by the wrong status check.
>
> For the application, the general method of MSG_FASTOPEN likes
>
> fd = socket(...)
> /* rather than connect */
> sendto(fd, data, len, MSG_FASTOPEN)
>
> Hence, We need to check the flag before state check, because the sock state
> here is always SMC_INIT when applications tries MSG_FASTOPEN. Once we
> found unsupported options, fallback it to TCP.
>
> Fixes: ee9dfbef02d1 ("net/smc: handle sockopts forcing fallback")
> Signed-off-by: D. Wythe <alibuda@linux.alibaba.com>
> ---
> net/smc/af_smc.c | 26 ++++++++++++++++----------
> 1 file changed, 16 insertions(+), 10 deletions(-)
>
> diff --git a/net/smc/af_smc.c b/net/smc/af_smc.c
> index b233c94..fd80879 100644
> --- a/net/smc/af_smc.c
> +++ b/net/smc/af_smc.c
> @@ -2662,24 +2662,30 @@ static int smc_sendmsg(struct socket *sock, struct msghdr *msg, size_t len)
> int rc = -EPIPE;
>
> smc = smc_sk(sk);
> - lock_sock(sk);
> - if ((sk->sk_state != SMC_ACTIVE) &&
> - (sk->sk_state != SMC_APPCLOSEWAIT1) &&
> - (sk->sk_state != SMC_INIT))
> - goto out;
>
> + /* SMC do not support connect with fastopen */
> if (msg->msg_flags & MSG_FASTOPEN) {
> + rc = -EINVAL;
> + lock_sock(sk);
> + /* not perform connect yet, fallback it */
> if (sk->sk_state == SMC_INIT && !smc->connect_nonblock) {
> rc = smc_switch_to_fallback(smc, SMC_CLC_DECL_OPTUNSUPP);
> - if (rc)
> - goto out;
> - } else {
> - rc = -EINVAL;
> - goto out;
> + /* fallback success */
> + if (rc == 0)
> + goto fallback; /* with sock lock hold */
> }
> + release_sock(sk);
> + return rc;
> }
>
> + lock_sock(sk);
> + if (sk->sk_state != SMC_ACTIVE &&
> + sk->sk_state != SMC_APPCLOSEWAIT1 &&
> + sk->sk_state != SMC_INIT)
> + goto out;
> +
> if (smc->use_fallback) {
> +fallback:
> rc = smc->clcsock->ops->sendmsg(smc->clcsock, msg, len);
> } else {
> rc = smc_tx_sendmsg(smc, msg, len);
> --
> 1.8.3.1
Probably I messed something this, as this is *compile tested only*.
But as the code at the out label looks like this:
out:
release_sock(sk);
return rc;
And smc_switch_to_fallback sets smc->use_fallback,
I wonder if the following is a bit nicer:
diff --git a/net/smc/af_smc.c b/net/smc/af_smc.c
index a4cccdfdc00a..5d5c19e53b77 100644
--- a/net/smc/af_smc.c
+++ b/net/smc/af_smc.c
@@ -2657,16 +2657,14 @@ static int smc_sendmsg(struct socket *sock, struct msghdr *msg, size_t len)
{
struct sock *sk = sock->sk;
struct smc_sock *smc;
- int rc = -EPIPE;
+ int rc;
smc = smc_sk(sk);
lock_sock(sk);
- if ((sk->sk_state != SMC_ACTIVE) &&
- (sk->sk_state != SMC_APPCLOSEWAIT1) &&
- (sk->sk_state != SMC_INIT))
- goto out;
+ /* SMC does not support connect with fastopen */
if (msg->msg_flags & MSG_FASTOPEN) {
+ /* not connected yet, fallback */
if (sk->sk_state == SMC_INIT && !smc->connect_nonblock) {
rc = smc_switch_to_fallback(smc, SMC_CLC_DECL_OPTUNSUPP);
if (rc)
@@ -2675,6 +2673,11 @@ static int smc_sendmsg(struct socket *sock, struct msghdr *msg, size_t len)
rc = -EINVAL;
goto out;
}
+ } else if (sk->sk_state != SMC_ACTIVE &&
+ sk->sk_state != SMC_APPCLOSEWAIT1 &&
+ sk->sk_state != SMC_INIT) {
+ rc = -EPIPE;
+ goto out;
}
if (smc->use_fallback) {
next prev parent reply other threads:[~2023-03-06 12:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 4:08 [PATCH net] net/smc: fix fallback failed while sendmsg with fastopen D. Wythe
2023-03-06 12:24 ` Simon Horman [this message]
2023-03-06 16:01 ` D. Wythe
2023-03-06 16:02 ` Simon Horman
2023-03-06 16:09 ` 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=ZAXbkUh4h2rIJdR2@corigine.com \
--to=simon.horman@corigine.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;
as well as URLs for NNTP newsgroup(s).