From: Yonglong Li <liyonglong@chinatelecom.cn> To: Mat Martineau <mathew.j.martineau@linux.intel.com> Cc: mptcp@lists.linux.dev Subject: Re: [PATCH v3 3/4] mptcp: build ADD_ADDR/echo-ADD_ADDR option according pm.add_signal Date: Fri, 18 Jun 2021 09:24:36 +0800 [thread overview] Message-ID: <43f90eee-f256-9e1a-7ef3-84130885e0e3@chinatelecom.cn> (raw) In-Reply-To: <d4b0a07d-72af-9a9d-69d3-d63f65ee367@linux.intel.com> On 2021/6/18 8:25, Mat Martineau wrote: > > This goto isn't quite right. It jumps below with opts and remaining already modified, and may end up modifying 'remaining' again. > > Would be better to separate the logic for sending echo-vs-signal, so the goto isn't necessary. Thanks for your review. The goto logic is not right indeed. I will separate the logic for sending echo-vs-signal > >> + else if (remaining < len) >> + goto out; >> + remaining -= len; >> + *size += len; >> + opts->remote = remote; >> + flags = (u8)~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_signal_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; >> + flags = (u8)~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, flags | msk->pm.addr_signal); >> + spin_unlock_bh(&msk->pm.lock); > > This would set bits in msk->pm.addr_signal rather than clear them. Did you intend '&' instead of '|'? Sorry for this mistake. :(
next prev parent reply other threads:[~2021-06-18 1:24 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-17 9:14 [PATCH v3 0/4] mptcp: fix conflicts when using pm.add_signal in ADD_ADDR/echo and RM_ADDR process Yonglong Li 2021-06-17 9:14 ` [PATCH v3 1/4] mptcp: fix ADD_ADDR and RM_ADDR maybe flush addr_signal each other Yonglong Li 2021-06-17 21:06 ` Mat Martineau 2021-06-17 9:14 ` [PATCH v3 2/4] mptcp: make MPTCP_ADD_ADDR_SIGNAL and MPTCP_ADD_ADDR_ECHO separate Yonglong Li 2021-06-17 9:14 ` [PATCH v3 3/4] mptcp: build ADD_ADDR/echo-ADD_ADDR option according pm.add_signal Yonglong Li 2021-06-17 12:37 ` Geliang Tang 2021-06-18 1:10 ` Yonglong Li 2021-06-17 19:22 ` kernel test robot 2021-06-18 0:25 ` Mat Martineau 2021-06-18 1:24 ` Yonglong Li [this message] 2021-06-17 9:14 ` [PATCH v3 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=43f90eee-f256-9e1a-7ef3-84130885e0e3@chinatelecom.cn \ --to=liyonglong@chinatelecom.cn \ --cc=mathew.j.martineau@linux.intel.com \ --cc=mptcp@lists.linux.dev \ --subject='Re: [PATCH v3 3/4] mptcp: build ADD_ADDR/echo-ADD_ADDR option according pm.add_signal' \ /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
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).