All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni at redhat.com>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [PATCH mptcp-next] Squash to "mptcp: only admit explicitly supported sockopt"
Date: Thu, 11 Mar 2021 11:43:37 +0100	[thread overview]
Message-ID: <246241bfed0aa8cc775699c530786ad813e10c97.camel@redhat.com> (raw)
In-Reply-To: 20210311101127.1774603-1-matthieu.baerts@tessares.net

[-- Attachment #1: Type: text/plain, Size: 1268 bytes --]

On Thu, 2021-03-11 at 11:11 +0100, Matthieu Baerts wrote:
> SO_SNDTIMEO_{OLD,NEW} were missing in the list. They are considered as
> "quite common but need a better implementation".
> 
> Indeed, as mentioned by Paolo: these settings are applied only to the
> first subflow, while mptcp_recvmsg()/mptcp_sendmsg() will look for the
> timeout value in the msk socket.
> 
> At least with these patches, we can have MPTCP BPF selftest passing:
> 
>   ./test_progs -n 66
> 
> Reported-and-tested-by: Geliang Tang <geliangtang(a)gmail.com>
> Signed-off-by: Matthieu Baerts <matthieu.baerts(a)tessares.net>
> ---
> 
> Notes:
>     to be squashed in "mptcp: only admit explicitly supported sockopt"
> 
>  net/mptcp/sockopt.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/net/mptcp/sockopt.c b/net/mptcp/sockopt.c
> index 3eda9127debb..fb98fab252df 100644
> --- a/net/mptcp/sockopt.c
> +++ b/net/mptcp/sockopt.c
> @@ -110,6 +110,8 @@ static bool mptcp_supported_sockopt(int level, int optname)
>  		case SO_RCVLOWAT:
>  		case SO_RCVTIMEO_OLD:
>  		case SO_RCVTIMEO_NEW:
> +		case SO_SNDTIMEO_OLD:
> +		case SO_SNDTIMEO_NEW:
>  		case SO_MARK:
>  		case SO_INCOMING_CPU:
>  		case SO_BINDTOIFINDEX:

LGTM! 

Thanks,

Paolo

             reply	other threads:[~2021-03-11 10:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11 10:43 Paolo Abeni [this message]
2021-03-11 11:05 [MPTCP] Re: [PATCH mptcp-next] Squash to "mptcp: only admit explicitly supported sockopt" 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=246241bfed0aa8cc775699c530786ad813e10c97.camel@redhat.com \
    --to=unknown@example.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.