From: Geliang Tang <geliang.tang@suse.com>
To: Paolo Abeni <pabeni@redhat.com>,
Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next 1/7] mptcp: fix removing ids bitmap
Date: Mon, 10 Jan 2022 20:33:18 +0800 [thread overview]
Message-ID: <20220110123318.GA3145@bogon> (raw)
In-Reply-To: <b3999648a78756fe4551b821d26b2d0e8423ee44.camel@redhat.com>
On Mon, Jan 10, 2022 at 12:40:14PM +0100, Paolo Abeni wrote:
> On Mon, 2022-01-10 at 11:29 +0800, Geliang Tang wrote:
> > In mptcp_pm_nl_rm_addr_or_subflow(), the bit of rm_list->ids[i] in the
> > id_avail_bitmap should be set, not rm_list->ids[1]. This patch fixed it.
> >
> > Fixes: 86e39e04482b ("mptcp: keep track of local endpoint still available for each msk")
> > Signed-off-by: Geliang Tang <geliang.tang@suse.com>
> > ---
> > net/mptcp/pm_netlink.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/net/mptcp/pm_netlink.c b/net/mptcp/pm_netlink.c
> > index f12effa71942..47ad00d01cf2 100644
> > --- a/net/mptcp/pm_netlink.c
> > +++ b/net/mptcp/pm_netlink.c
> > @@ -777,7 +777,7 @@ 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[1], msk->pm.id_avail_bitmap);
> > + __set_bit(rm_list->ids[i], msk->pm.id_avail_bitmap);
> > if (!removed)
> > continue;
> >
>
> LGTM!
>
> Acked-by: Paolo Abeni <pabeni@redhat.com>
>
> I think this one could be spooled independently from the other patches,
> so it could land on -net early.
>
> WDYT?
Great!
Matt, could you please help me to update the subject of this patch to
"mptcp: fix removing ids bitmap setting" when merging it?
Thanks,
-Geliang
>
> Thanks!
>
> Paolo
>
next prev parent reply other threads:[~2022-01-10 12:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 3:29 [PATCH mptcp-next 0/7] fullmesh flag setting support Geliang Tang
2022-01-10 3:29 ` [PATCH mptcp-next 1/7] mptcp: fix removing ids bitmap Geliang Tang
2022-01-10 11:40 ` Paolo Abeni
2022-01-10 12:33 ` Geliang Tang [this message]
2022-01-10 3:30 ` [PATCH mptcp-next 2/7] mptcp: add clear_flags in pm_netlink Geliang Tang
2022-01-10 11:38 ` Paolo Abeni
2022-01-10 12:35 ` Geliang Tang
2022-01-10 15:59 ` Paolo Abeni
2022-01-10 3:30 ` [PATCH mptcp-next 3/7] selftests: mptcp: add clear_flags in pm_nl_ctl Geliang Tang
2022-01-10 3:30 ` [PATCH mptcp-next 4/7] selftests: mptcp: add clear_flags in mptcp_join.sh Geliang Tang
2022-01-10 3:30 ` [PATCH mptcp-next 5/7] mptcp: set fullmesh flag in pm_netlink Geliang Tang
2022-01-10 3:30 ` [PATCH mptcp-next 6/7] selftests: mptcp: set fullmesh flag in pm_nl_ctl Geliang Tang
2022-01-10 3:30 ` [PATCH mptcp-next 7/7] selftests: mptcp: add fullmesh setting tests Geliang Tang
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=20220110123318.GA3145@bogon \
--to=geliang.tang@suse.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