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-next v2 05/36] mptcp: add lookup_addr for userspace pm
Date: Wed, 30 Oct 2024 19:21:42 +0100 [thread overview]
Message-ID: <af13381b-4bc8-4735-8c0d-abca4ae6c48e@kernel.org> (raw)
In-Reply-To: <6d30431fd64e8c17d163ab5656838e1c3be78b97.1729588019.git.tanggeliang@kylinos.cn>
Hi Geliang,
On 22/10/2024 11:14, Geliang Tang wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
>
> Like __lookup_addr() helper in pm_netlink.c, a new helper
> mptcp_userspace_pm_lookup_addr() is also defined in pm_userspace.c.
> It looks up the corresponding mptcp_pm_addr_entry address in
> userspace_pm_local_addr_list through the passed "addr" parameter
> and returns it.
>
> This helper can be used in mptcp_userspace_pm_delete_local_addr(),
> mptcp_userspace_pm_get_local_id() and mptcp_userspace_pm_is_backup()
> to simplify the code.
>
> Signed-off-by: Geliang Tang <tanggeliang@kylinos.cn>
> ---
> net/mptcp/pm_userspace.c | 56 +++++++++++++++++++++-------------------
> 1 file changed, 29 insertions(+), 27 deletions(-)
>
> diff --git a/net/mptcp/pm_userspace.c b/net/mptcp/pm_userspace.c
> index 3fb5713cd988..ce0f7131c701 100644
> --- a/net/mptcp/pm_userspace.c
> +++ b/net/mptcp/pm_userspace.c
> @@ -26,6 +26,18 @@ void mptcp_free_local_addr_list(struct mptcp_sock *msk)
> }
> }
>
> +static struct mptcp_pm_addr_entry *
> +mptcp_userspace_pm_lookup_addr(struct mptcp_sock *msk, const struct mptcp_addr_info *addr)
When possible, can you try to limit to 80 chars per line?
See: https://github.com/linux-netdev/nipa/pull/41
Using more than 80 is allowed, but it should be restricted to cases
where using less than 80 chars affects the readability, e.g. not to
break 'entry->flags & MY_SPECIFIC_FLAG' in two lines, etc. The idea is
not to abuse of that.
Here for example, it is easy to go to the new line after the ','.
> +{
> + struct mptcp_pm_addr_entry *entry, *tmp;
> +
> + mptcp_for_each_address_safe(msk, entry, tmp) {
Why do you need the '_safe' alternative here? You only return an entry
from the list, and you stop: no need to continue after having modified
the list here as far as I can see, no?
Also, something very important: here you are presenting the modification
as a simple refactoring, but it does change the behaviour: the '_safe'
version is used everywhere, which was not the case before. When you do
something like that, please mention it in the commit message! Without
that, a reviewer might not notice it "OK, just a refactoring", and
developers might wonder later why this was done. I then recommend to
always add either something like:
- "No behaviour change intended here."
- or "Please note that now <something different is done> for <these
cases>, but that's OK to do so <because ...>."
> + if (mptcp_addresses_equal(&entry->addr, addr, false))
> + return entry;
> + }
> + return NULL;
> +}
> +
> static int mptcp_userspace_pm_append_new_local_addr(struct mptcp_sock *msk,
> struct mptcp_pm_addr_entry *entry,
> bool needs_id)
> @@ -90,22 +102,20 @@ static int mptcp_userspace_pm_append_new_local_addr(struct mptcp_sock *msk,
> static int mptcp_userspace_pm_delete_local_addr(struct mptcp_sock *msk,
> struct mptcp_pm_addr_entry *addr)
> {
> - struct mptcp_pm_addr_entry *entry, *tmp;
> struct sock *sk = (struct sock *)msk;
> + struct mptcp_pm_addr_entry *entry;
>
> - mptcp_for_each_address_safe(msk, entry, tmp) {
> - if (mptcp_addresses_equal(&entry->addr, &addr->addr, false)) {
> - /* TODO: a refcount is needed because the entry can
> - * be used multiple times (e.g. fullmesh mode).
> - */
> - list_del_rcu(&entry->list);
> - sock_kfree_s(sk, entry, sizeof(*entry));
> - msk->pm.local_addr_used--;
> - return 0;
> - }
> - }
> -
> - return -EINVAL;
> + entry = mptcp_userspace_pm_lookup_addr(msk, &addr->addr);
> + if (!entry)
> + return -EINVAL;
> +
> + /* TODO: a refcount is needed because the entry can
> + * be used multiple times (e.g. fullmesh mode).
> + */
(Not related to this commit: I wonder if the TODO still makes sense. We
had some discussions with Mat, and I think the conclusion was that it
was OK, but I don't remember why)
> + list_del_rcu(&entry->list);
> + sock_kfree_s(sk, entry, sizeof(*entry));
> + msk->pm.local_addr_used--;
> + return 0;
> }
>
> static struct mptcp_pm_addr_entry *
> @@ -123,17 +133,12 @@ mptcp_userspace_pm_lookup_addr_by_id(struct mptcp_sock *msk, unsigned int id)
> int mptcp_userspace_pm_get_local_id(struct mptcp_sock *msk,
> struct mptcp_addr_info *skc)
> {
> - struct mptcp_pm_addr_entry *entry = NULL, *e, new_entry;
> + struct mptcp_pm_addr_entry *entry = NULL, new_entry;
> __be16 msk_sport = ((struct inet_sock *)
> inet_sk((struct sock *)msk))->inet_sport;
>
> spin_lock_bh(&msk->pm.lock);
> - mptcp_for_each_address(msk, e) {
> - if (mptcp_addresses_equal(&e->addr, skc, false)) {
> - entry = e;
> - break;
> - }
> - }
> + entry = mptcp_userspace_pm_lookup_addr(msk, skc);
> spin_unlock_bh(&msk->pm.lock);
> if (entry)
> return entry->addr.id;
> @@ -156,12 +161,9 @@ bool mptcp_userspace_pm_is_backup(struct mptcp_sock *msk,
> bool backup = false;
>
> spin_lock_bh(&msk->pm.lock);
> - mptcp_for_each_address(msk, entry) {
> - if (mptcp_addresses_equal(&entry->addr, skc, false)) {
> - backup = !!(entry->flags & MPTCP_PM_ADDR_FLAG_BACKUP);
> - break;
> - }
> - }
> + entry = mptcp_userspace_pm_lookup_addr(msk, skc);
> + if (entry)
> + backup = !!(entry->flags & MPTCP_PM_ADDR_FLAG_BACKUP);
> spin_unlock_bh(&msk->pm.lock);
>
> return backup;
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2024-10-30 18:21 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 9:14 [PATCH mptcp-next v2 00/36] BPF path manager Geliang Tang
2024-10-22 9:14 ` [PATCH mptcp-next v2 01/36] mptcp: drop else in mptcp_pm_addr_families_match Geliang Tang
2024-10-22 17:01 ` Matthieu Baerts
2024-10-23 9:53 ` Geliang Tang
2024-10-22 9:14 ` [PATCH mptcp-next v2 02/36] mptcp: use __lookup_addr in pm_netlink Geliang Tang
2024-10-22 17:09 ` Matthieu Baerts
2024-10-23 9:59 ` Geliang Tang
2024-10-23 10:03 ` Matthieu Baerts
2024-10-23 10:06 ` Geliang Tang
2024-10-22 9:14 ` [PATCH mptcp-next v2 03/36] mptcp: add mptcp_for_each_address macros Geliang Tang
2024-10-30 18:20 ` Matthieu Baerts
2024-10-31 7:55 ` Geliang Tang
2024-10-22 9:14 ` [PATCH mptcp-next v2 04/36] mptcp: use sock_kfree_s instead of kfree Geliang Tang
2024-10-30 18:21 ` Matthieu Baerts
2024-10-31 7:43 ` Geliang Tang
2024-10-22 9:14 ` [PATCH mptcp-next v2 05/36] mptcp: add lookup_addr for userspace pm Geliang Tang
2024-10-30 18:21 ` Matthieu Baerts [this message]
2024-10-22 9:14 ` [PATCH mptcp-next v2 06/36] mptcp: add mptcp_userspace_pm_get_sock helper Geliang Tang
2024-10-30 18:23 ` Matthieu Baerts
2024-10-22 9:14 ` [PATCH mptcp-next v2 07/36] mptcp: make three pm wrappers static Geliang Tang
2024-10-30 18:31 ` Matthieu Baerts
2024-10-31 7:58 ` Geliang Tang
2024-10-31 16:33 ` Matthieu Baerts
2024-10-22 9:14 ` [PATCH mptcp-next v2 08/36] mptcp: drop skb parameter of get_addr Geliang Tang
2024-10-22 9:14 ` [PATCH mptcp-next v2 09/36] mptcp: add id parameter for get_addr Geliang Tang
2024-10-22 9:14 ` [PATCH mptcp-next v2 10/36] mptcp: add addr " Geliang Tang
2024-10-22 9:14 ` [PATCH mptcp-next v2 11/36] mptcp: reuse sending nlmsg code in get_addr Geliang Tang
2024-10-22 9:14 ` [PATCH mptcp-next v2 12/36] mptcp: change info of get_addr as const Geliang Tang
2024-10-31 18:41 ` Matthieu Baerts
2024-10-22 9:14 ` [PATCH mptcp-next v2 13/36] mptcp: add struct mptcp_id_bitmap Geliang Tang
2024-10-31 18:45 ` Matthieu Baerts
2024-11-04 9:12 ` Geliang Tang
2024-11-04 10:16 ` Matthieu Baerts
2024-10-22 9:14 ` [PATCH mptcp-next v2 14/36] mptcp: refactor dump_addr with id bitmap Geliang Tang
2024-11-04 17:18 ` Matthieu Baerts
2024-10-22 9:14 ` [PATCH mptcp-next v2 15/36] mptcp: refactor dump_addr with get_addr Geliang Tang
2024-10-22 9:14 ` [PATCH mptcp-next v2 16/36] mptcp: reuse sending nlmsg code in dump_addr Geliang Tang
2024-10-22 9:14 ` [PATCH mptcp-next v2 17/36] mptcp: update local address flags when setting it Geliang Tang
2024-11-04 18:20 ` Matthieu Baerts
2024-10-22 9:14 ` [PATCH mptcp-next v2 18/36] mptcp: change rem type of set_flags Geliang Tang
2024-10-22 9:14 ` [PATCH mptcp-next v2 19/36] mptcp: drop skb parameter " Geliang Tang
2024-10-22 9:14 ` [PATCH mptcp-next v2 20/36] mptcp: add loc and rem for set_flags Geliang Tang
2024-11-04 18:36 ` Matthieu Baerts
2024-10-22 9:14 ` [PATCH mptcp-next v2 21/36] mptcp: update address type of get_local_id Geliang Tang
2024-11-04 18:48 ` Matthieu Baerts
2024-11-07 7:35 ` Geliang Tang
2024-10-22 9:14 ` [PATCH mptcp-next v2 22/36] mptcp: change is_backup interfaces as get_flags Geliang Tang
2024-11-04 18:55 ` Matthieu Baerts
2025-01-14 9:27 ` Geliang Tang
2024-10-22 9:14 ` [PATCH mptcp-next v2 23/36] mptcp: drop struct mptcp_pm_local Geliang Tang
2024-11-04 19:08 ` Matthieu Baerts
2024-11-07 7:29 ` Geliang Tang
2024-11-07 10:00 ` Matthieu Baerts
2024-11-07 10:19 ` Geliang Tang
2024-11-10 4:32 ` Geliang Tang
2024-11-27 6:17 ` Geliang Tang
2024-10-22 9:14 ` [PATCH mptcp-next v2 24/36] mptcp: drop struct mptcp_pm_add_entry Geliang Tang
2024-11-04 19:13 ` Matthieu Baerts
2024-10-22 9:14 ` [PATCH mptcp-next v2 25/36] mptcp: change local type of subflow_destroy Geliang Tang
2024-10-22 9:14 ` [PATCH mptcp-next v2 26/36] mptcp: hold pm lock when deleting entry Geliang Tang
2024-11-04 19:17 ` Matthieu Baerts
2024-10-22 9:14 ` [PATCH mptcp-next v2 27/36] mptcp: rename mptcp_pm_remove_addrs Geliang Tang
2024-11-04 19:24 ` Matthieu Baerts
2024-10-22 9:14 ` [PATCH mptcp-next v2 28/36] mptcp: drop free_list for deleting entries Geliang Tang
2024-11-04 19:27 ` Matthieu Baerts
2024-10-22 9:14 ` [PATCH mptcp-next v2 29/36] mptcp: define struct mptcp_pm_ops Geliang Tang
2024-10-22 9:14 ` [PATCH mptcp-next v2 30/36] mptcp: implement userspace pm interfaces Geliang Tang
2024-10-22 9:14 ` [PATCH mptcp-next v2 31/36] mptcp: register default userspace pm Geliang Tang
2024-10-22 9:14 ` [PATCH mptcp-next v2 32/36] bpf: Add mptcp path manager struct_ops Geliang Tang
2024-10-22 9:14 ` [PATCH mptcp-next v2 33/36] bpf: Register mptcp struct_ops kfunc set Geliang Tang
2024-10-22 9:14 ` [PATCH mptcp-next v2 34/36] Squash to "bpf: Export mptcp packet scheduler helpers" Geliang Tang
2024-10-22 9:14 ` [PATCH mptcp-next v2 35/36] selftests/bpf: Add mptcp userspace pm subtest Geliang Tang
2024-10-22 9:14 ` [PATCH mptcp-next v2 36/36] selftests/bpf: Add mptcp bpf path manager subtest Geliang Tang
2024-10-22 10:12 ` [PATCH mptcp-next v2 00/36] BPF path manager MPTCP CI
2024-10-22 10:24 ` MPTCP CI
2024-11-04 19:31 ` Matthieu Baerts
2024-11-05 10:12 ` 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=af13381b-4bc8-4735-8c0d-abca4ae6c48e@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