mptcp.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Yonglong Li <liyonglong@chinatelecom.cn>
To: Mat Martineau <mathew.j.martineau@linux.intel.com>
Cc: mptcp@lists.linux.dev, pabeni@redhat.com,
	matthieu.baerts@tessares.net, geliangtang@gmail.com
Subject: Re: [PATCH v2 3/4] mptcp: build ADD_ADDR/echo-ADD_ADDR option according pm.add_signal
Date: Thu, 17 Jun 2021 10:31:52 +0800	[thread overview]
Message-ID: <883a9ce8-8943-2c94-5acf-97034445e789@chinatelecom.cn> (raw)
In-Reply-To: <ff8a313c-faca-d5b8-58be-802b795f8b8b@linux.intel.com>



On 2021/6/17 7:47, Mat Martineau wrote:
> On Tue, 15 Jun 2021, Yonglong Li wrote:
> 
>> according MPTCP_ADD_ADDR_SIGNAL and MPTCP_ADD_ADDR_ECHO flag build
>> ADD_ADDR/echo-ADD_ADDR option
>>
>> add a suboptions type OPTION_MPTCP_ADD_ECHO to mark as echo option
>>
>> Signed-off-by: Yonglong Li <liyonglong@chinatelecom.cn>
>> ---
>> net/mptcp/options.c  | 161 +++++++++++++++++++++++++++++++++------------------
>> net/mptcp/pm.c       |  32 ++++------
>> net/mptcp/protocol.h |  13 +++--
>> 3 files changed, 124 insertions(+), 82 deletions(-)
>>
>> diff --git a/net/mptcp/options.c b/net/mptcp/options.c
>> index 1aec016..8875ba4 100644
>> --- a/net/mptcp/options.c
>> +++ b/net/mptcp/options.c
>> @@ -655,43 +655,72 @@ static bool mptcp_established_options_add_addr(struct sock *sk, struct sk_buff *
>>     struct mptcp_sock *msk = mptcp_sk(subflow->conn);
>>     bool drop_other_suboptions = false;
>>     unsigned int opt_size = *size;
>> -    bool echo;
>> -    bool port;
>> +    struct mptcp_addr_info remote;
>> +    struct mptcp_addr_info local;
>> +    int ret = false;
>> +    u8 add_addr;
>>     int len;
>>
>> -    if ((mptcp_pm_should_add_signal_ipv6(msk) ||
>> -         mptcp_pm_should_add_signal_port(msk) ||
>> -         mptcp_pm_should_add_signal_echo(msk)) &&
>> -        skb && skb_is_tcp_pure_ack(skb)) {
>> -        pr_debug("drop other suboptions");
>> -        opts->suboptions = 0;
>> -        opts->ext_copy.use_ack = 0;
>> -        opts->ext_copy.use_map = 0;
>> -        remaining += opt_size;
>> -        drop_other_suboptions = true;
>> -    }
>> -
>> -    if (!mptcp_pm_should_add_signal(msk) ||
>> -        !(mptcp_pm_add_addr_signal(msk, remaining, &opts->addr, &echo, &port)))
>> -        return false;
>> -
>> -    len = mptcp_add_addr_len(opts->addr.family, echo, port);
>> -    if (remaining < len)
>> -        return false;
>> -
>> -    *size = len;
>> -    if (drop_other_suboptions)
>> -        *size -= opt_size;
>> -    opts->suboptions |= OPTION_MPTCP_ADD_ADDR;
>> -    if (!echo) {
>> +    if (!mptcp_pm_should_add_signal(msk))
>> +        goto out;
>> +
>> +    *size = 0;
>> +    mptcp_pm_add_addr_signal(msk, &local, &remote, &add_addr);
> 
> Return value of this function is ignored, so it shouldn't return bool anymore. However, read below about locking and handling of the add_addr value before making changes.
> 
>> +    if (mptcp_pm_should_add_signal_echo(msk)) {
>> +        if (skb && skb_is_tcp_pure_ack(skb)) {
>> +            pr_debug("drop other suboptions");
>> +            opts->suboptions = 0;
>> +            opts->ext_copy.use_ack = 0;
>> +            opts->ext_copy.use_map = 0;
>> +            remaining += opt_size;
>> +            drop_other_suboptions = true;
>> +        }
>> +        len = mptcp_add_addr_len(remote.family, true, !!remote.port);
>> +        if (remaining < len && mptcp_pm_should_add_addr(msk))
>> +            goto add_addr;
>> +        else if (remaining < len)
>> +            goto out;
>> +        remaining -= len;
>> +        *size += len;
>> +        opts->remote = remote;
>> +        add_addr &= ~BIT(MPTCP_ADD_ADDR_ECHO);
>> +        opts->suboptions |= OPTION_MPTCP_ADD_ECHO;
>> +        pr_debug("addr_id=%d, echo=1, port=%d addr_signal:%x",
>> +             opts->remote.id, ntohs(opts->remote.port), add_addr);
>> +    } else if (mptcp_pm_should_add_addr(msk)) {
>> +add_addr:
>> +        if ((local.family == AF_INET6 || local.port) && skb &&
>> +            skb_is_tcp_pure_ack(skb)) {
>> +            pr_debug("drop other suboptions");
>> +            opts->suboptions = 0;
>> +            opts->ext_copy.use_ack = 0;
>> +            opts->ext_copy.use_map = 0;
>> +            remaining += opt_size;
>> +            drop_other_suboptions = true;
>> +        }
>> +        len = mptcp_add_addr_len(local.family, false, !!local.port);
>> +        if (remaining < len)
>> +            goto out;
>> +        *size += len;
>> +        opts->addr = local;
>>         opts->ahmac = add_addr_generate_hmac(msk->local_key,
>>                              msk->remote_key,
>>                              &opts->addr);
>> +        opts->suboptions |= OPTION_MPTCP_ADD_ADDR;
>> +        add_addr &= ~BIT(MPTCP_ADD_ADDR_SIGNAL);
>> +        pr_debug("addr_id=%d, ahmac=%llu, echo=0, port=%d, addr_signal:%x",
>> +             opts->addr.id, opts->ahmac, ntohs(opts->addr.port), add_addr);
>>     }
>> -    pr_debug("addr_id=%d, ahmac=%llu, echo=%d, port=%d",
>> -         opts->addr.id, opts->ahmac, echo, ntohs(opts->addr.port));
>>
>> -    return true;
>> +    if (drop_other_suboptions)
>> +        *size -= opt_size;
>> +    spin_lock_bh(&msk->pm.lock);
>> +    WRITE_ONCE(msk->pm.addr_signal, add_addr);
>> +    spin_unlock_bh(&msk->pm.lock);
> 
> It's not safe to do a read-modify-write of msk->pm.addr_signal if the pm lock is not held for the *entire* time. Another thread could have set or cleared any other bit in msk->pm_addr_signal while the lock was not held here, and this code would overwrite any of those changes.

right. Thanks for you review. I will prepare v2 patch.

> 
>> +    ret = true;
>> +
>> +out:
>> +    return ret;
>> }
>>
>> static bool mptcp_established_options_rm_addr(struct sock *sk,
> 
> -- 
> Mat Martineau
> Intel
> 
> 

  reply	other threads:[~2021-06-17  2:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-15  1:31 [PATCH v2 0/4] mptcp: fix conflicts when using pm.add_signal in ADD_ADDR/echo and RM_ADDR process Yonglong Li
2021-06-15  1:31 ` [PATCH v2 1/4] mptcp: fix ADD_ADDR and RM_ADDR maybe flush addr_signal each other Yonglong Li
2021-06-16 23:30   ` Mat Martineau
2021-06-17  2:13     ` Yonglong Li
2021-06-15  1:31 ` [PATCH v2 2/4] mptcp: make MPTCP_ADD_ADDR_SIGNAL and MPTCP_ADD_ADDR_ECHO separate Yonglong Li
2021-06-16 23:35   ` Mat Martineau
2021-06-15  1:31 ` [PATCH v2 3/4] mptcp: build ADD_ADDR/echo-ADD_ADDR option according pm.add_signal Yonglong Li
2021-06-16 23:47   ` Mat Martineau
2021-06-17  2:31     ` Yonglong Li [this message]
2021-06-15  1:31 ` [PATCH v2 4/4] mptcp: remove MPTCP_ADD_ADDR_IPV6 and MPTCP_ADD_ADDR_PORT Yonglong Li

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=883a9ce8-8943-2c94-5acf-97034445e789@chinatelecom.cn \
    --to=liyonglong@chinatelecom.cn \
    --cc=geliangtang@gmail.com \
    --cc=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;
as well as URLs for NNTP newsgroup(s).