From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: mptcp@lists.linux.dev, Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH mptcp-next] mptcp: sockopt: use new helper for TCP_DEFER_ACCEPT
Date: Wed, 28 Sep 2022 12:05:26 -0700 (PDT) [thread overview]
Message-ID: <49a8b516-1dd6-7abd-8be5-5a3f6fd441fb@linux.intel.com> (raw)
In-Reply-To: <20220928091852.1933333-1-matthieu.baerts@tessares.net>
On Wed, 28 Sep 2022, Matthieu Baerts wrote:
> mptcp_setsockopt_sol_tcp_defer() was doing the same thing as
> mptcp_setsockopt_first_sf_only() except for the returned code in case of
> error.
>
> Ignoring the error is needed to mimic how TCP_DEFER_ACCEPT is handled
> when used with "plain" TCP sockets.
>
> The specific function for TCP_DEFER_ACCEPT can be replaced by the new
> mptcp_setsockopt_first_sf_only() helper and errors can be ignored to
> stay compatible with TCP. A bit of cleanup.
>
> Suggested-by: Paolo Abeni <pabeni@redhat.com>
> Suggested-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
> Signed-off-by: Matthieu Baerts <matthieu.baerts@tessares.net>
Looks good to me, thanks!
Reviewed-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
> ---
> net/mptcp/sockopt.c | 16 +++-------------
> 1 file changed, 3 insertions(+), 13 deletions(-)
>
> diff --git a/net/mptcp/sockopt.c b/net/mptcp/sockopt.c
> index 1857281a0dd5..f85e9bbfe86f 100644
> --- a/net/mptcp/sockopt.c
> +++ b/net/mptcp/sockopt.c
> @@ -758,18 +758,6 @@ static int mptcp_setsockopt_v4(struct mptcp_sock *msk, int optname,
> return -EOPNOTSUPP;
> }
>
> -static int mptcp_setsockopt_sol_tcp_defer(struct mptcp_sock *msk, sockptr_t optval,
> - unsigned int optlen)
> -{
> - struct socket *listener;
> -
> - listener = __mptcp_nmpc_socket(msk);
> - if (!listener)
> - return 0; /* TCP_DEFER_ACCEPT does not fail */
> -
> - return tcp_setsockopt(listener->sk, SOL_TCP, TCP_DEFER_ACCEPT, optval, optlen);
> -}
> -
> static int mptcp_setsockopt_first_sf_only(struct mptcp_sock *msk, int level, int optname,
> sockptr_t optval, unsigned int optlen)
> {
> @@ -810,7 +798,9 @@ static int mptcp_setsockopt_sol_tcp(struct mptcp_sock *msk, int optname,
> case TCP_NODELAY:
> return mptcp_setsockopt_sol_tcp_nodelay(msk, optval, optlen);
> case TCP_DEFER_ACCEPT:
> - return mptcp_setsockopt_sol_tcp_defer(msk, optval, optlen);
> + /* See tcp.c: TCP_DEFER_ACCEPT does not fail */
> + mptcp_setsockopt_first_sf_only(msk, SOL_TCP, optname, optval, optlen);
> + return 0;
> case TCP_FASTOPEN_CONNECT:
> case TCP_FASTOPEN_NO_COOKIE:
> return mptcp_setsockopt_first_sf_only(msk, SOL_TCP, optname,
>
> base-commit: 6711fbb5e6c8541f84685542127455c18145d559
> --
> 2.37.2
>
>
--
Mat Martineau
Intel
next prev parent reply other threads:[~2022-09-28 19:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 9:18 [PATCH mptcp-next] mptcp: sockopt: use new helper for TCP_DEFER_ACCEPT Matthieu Baerts
2022-09-28 9:46 ` Paolo Abeni
2022-09-28 10:00 ` Matthieu Baerts
2022-09-28 11:13 ` mptcp: sockopt: use new helper for TCP_DEFER_ACCEPT: Tests Results MPTCP CI
2022-09-28 19:05 ` Mat Martineau [this message]
2022-09-30 8:18 ` [PATCH mptcp-next] mptcp: sockopt: use new helper for TCP_DEFER_ACCEPT Matthieu Baerts
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=49a8b516-1dd6-7abd-8be5-5a3f6fd441fb@linux.intel.com \
--to=mathew.j.martineau@linux.intel.com \
--cc=matthieu.baerts@tessares.net \
--cc=mptcp@lists.linux.dev \
--cc=pabeni@redhat.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