MPTCP Linux Development
 help / color / mirror / Atom feed
From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next 1/6] mptcp: fix local endpoint acconting.
Date: Fri, 1 Jul 2022 17:04:26 -0700 (PDT)	[thread overview]
Message-ID: <1dc71764-4046-79c3-c6f-5c736d2d64c0@linux.intel.com> (raw)
In-Reply-To: <f0f5893c05f19d5076a9d03c84b65495f488fbf2.1656669391.git.pabeni@redhat.com>

On Fri, 1 Jul 2022, Paolo Abeni wrote:

> In mptcp_pm_nl_rm_addr_or_subflow() we always mark as availble
> the id corresponding to the just removed address.
>
> The used bitmap actually tracks only the local IDs: we must
> restrict the operation when a (local) subflow is removed.
>
> Fixes: a88c9e496937 ("mptcp: do not block subflows creation on errors")
> Signed-off-by: Paolo Abeni <pabeni@redhat.com>

Looks good to me. Ok to apply this one to the net branch, separate from 
the rest of the series?


For this single patch:
Reviewed-by: Mat Martineau <mathew.j.martineau@linux.intel.com>

> ---
> net/mptcp/pm_netlink.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/net/mptcp/pm_netlink.c b/net/mptcp/pm_netlink.c
> index 0a295acf99b8..f1909006a859 100644
> --- a/net/mptcp/pm_netlink.c
> +++ b/net/mptcp/pm_netlink.c
> @@ -800,7 +800,8 @@ static void mptcp_pm_nl_rm_addr_or_subflow(struct mptcp_sock *msk,
> 			removed = true;
> 			__MPTCP_INC_STATS(sock_net(sk), rm_type);
> 		}
> -		__set_bit(rm_list->ids[i], msk->pm.id_avail_bitmap);
> +		if (rm_type == MPTCP_MIB_RMSUBFLOW)
> +			__set_bit(rm_list->ids[i], msk->pm.id_avail_bitmap);
> 		if (!removed)
> 			continue;
>
> -- 
> 2.35.3
>
>
>

--
Mat Martineau
Intel

  reply	other threads:[~2022-07-02  0:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-01 10:05 [PATCH mptcp-next 0/6] mptcp: support for MPC prio exchange Paolo Abeni
2022-07-01 10:05 ` [PATCH mptcp-next 1/6] mptcp: fix local endpoint acconting Paolo Abeni
2022-07-02  0:04   ` Mat Martineau [this message]
2022-07-04  8:02     ` Paolo Abeni
2022-07-04 16:09       ` Matthieu Baerts
2022-07-01 10:05 ` [PATCH mptcp-next 2/6] mptcp: introduce and use mptcp_pm_send_ack() Paolo Abeni
2022-07-02  0:13   ` Mat Martineau
2022-07-04  8:06     ` Paolo Abeni
2022-07-01 10:05 ` [PATCH mptcp-next 3/6] mptcp: address lookup improvements Paolo Abeni
2022-07-01 10:05 ` [PATCH mptcp-next 4/6] mptcp: allow the in kernel PM to set MPC subflow priority Paolo Abeni
2022-07-01 10:05 ` [PATCH mptcp-next 5/6] mptcp: more accurate MPC endpoint tracking Paolo Abeni
2022-07-01 10:05 ` [PATCH mptcp-next 6/6] selftests: mptcp: add MPC backup tests Paolo Abeni

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=1dc71764-4046-79c3-c6f-5c736d2d64c0@linux.intel.com \
    --to=mathew.j.martineau@linux.intel.com \
    --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