From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang@kernel.org>, mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: Re: [PATCH mptcp-net 2/3] mptcp: update local address flags when setting it
Date: Tue, 5 Nov 2024 18:31:13 +0100 [thread overview]
Message-ID: <97e320e9-d466-4837-85b0-912686794912@kernel.org> (raw)
In-Reply-To: <72998c181b94560b3d1e1e5843250ee2815869ac.1730799589.git.tanggeliang@kylinos.cn>
Hi Geliang,
On 05/11/2024 10:40, Geliang Tang wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
>
> Just like in-kernel pm, when userspace pm does set_flags, it needs to send
> out MP_PRIO signal, and also modify the flags of the corresponding address
> entry in the local address list. This patch implements the missing logic.
>
> Use mptcp_userspace_pm_lookup_addr() helper to find the address entry on
> userspace_pm_local_addr_list, if bkup is true, set the flags of the address
> entry with FLAG_BACKUP, otherwise, clear FLAG_BACKUP.
>
> Fixes: 892f396c8e68 ("mptcp: netlink: issue MP_PRIO signals from userspace PMs")
> Signed-off-by: Geliang Tang <tanggeliang@kylinos.cn>
> ---
> net/mptcp/pm_userspace.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/net/mptcp/pm_userspace.c b/net/mptcp/pm_userspace.c
> index 9c622b0e3e6e..0c0f6f65accb 100644
> --- a/net/mptcp/pm_userspace.c
> +++ b/net/mptcp/pm_userspace.c
> @@ -562,6 +562,7 @@ int mptcp_userspace_pm_set_flags(struct sk_buff *skb, struct genl_info *info)
> struct nlattr *token = info->attrs[MPTCP_PM_ATTR_TOKEN];
> struct nlattr *attr = info->attrs[MPTCP_PM_ATTR_ADDR];
> struct net *net = sock_net(skb->sk);
> + struct mptcp_pm_addr_entry *entry;
> struct mptcp_sock *msk;
> int ret = -EINVAL;
> struct sock *sk;
> @@ -603,6 +604,16 @@ int mptcp_userspace_pm_set_flags(struct sk_buff *skb, struct genl_info *info)
> if (loc.flags & MPTCP_PM_ADDR_FLAG_BACKUP)
> bkup = 1;
>
> + spin_lock_bh(&msk->pm.lock);
> + entry = mptcp_userspace_pm_lookup_addr(msk, &loc.addr);
(Linked to my comment from the previous patch) Adding only the helper,
and squashing that in this patch here might be an option, but even that
can cause conflicts.
I think the simplest is not to add this small helper only used once for
the moment: so simply calling list_for_each_entry() here, and add the
following code inside it. WDYT?
> + if (entry) {
> + if (bkup)
> + entry->flags |= MPTCP_PM_ADDR_FLAG_BACKUP;
> + else
> + entry->flags &= ~MPTCP_PM_ADDR_FLAG_BACKUP;
> + }
> + spin_unlock_bh(&msk->pm.lock);
> +
> lock_sock(sk);
> ret = mptcp_pm_nl_mp_prio_send_ack(msk, &loc.addr, &rem.addr, bkup);
> release_sock(sk);
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2024-11-05 17:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 9:40 [PATCH mptcp-net 0/3] fixes for userspace pm Geliang Tang
2024-11-05 9:40 ` [PATCH mptcp-net 1/3] mptcp: add lookup_addr " Geliang Tang
2024-11-05 17:31 ` Matthieu Baerts
2024-11-05 9:40 ` [PATCH mptcp-net 2/3] mptcp: update local address flags when setting it Geliang Tang
2024-11-05 17:31 ` Matthieu Baerts [this message]
2024-11-05 9:41 ` [PATCH mptcp-net 3/3] mptcp: hold pm lock when deleting entry Geliang Tang
2024-11-05 11:25 ` [PATCH mptcp-net 0/3] fixes for userspace pm MPTCP CI
2024-11-05 15:40 ` MPTCP CI
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=97e320e9-d466-4837-85b0-912686794912@kernel.org \
--to=matttbe@kernel.org \
--cc=geliang@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=tanggeliang@kylinos.cn \
/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