From: Mat Martineau <martineau@kernel.org>
To: Geliang Tang <geliang@kernel.org>
Cc: mptcp@lists.linux.dev, Geliang Tang <tanggeliang@kylinos.cn>
Subject: Re: [PATCH mptcp-next v10 01/23] mptcp: add pm_has_addr_attr_id helper
Date: Tue, 30 Jan 2024 18:15:28 -0800 (PST) [thread overview]
Message-ID: <a4e54887-1155-26af-c8e1-9f4f28ca2be7@kernel.org> (raw)
In-Reply-To: <9d4caf4cbb5f75d8bc057cdd2f073c243a2dcf92.1705558030.git.tanggeliang@kylinos.cn>
On Thu, 18 Jan 2024, Geliang Tang wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
>
> This patch adds a new helper mptcp_pm_has_addr_attr_id() to check whether
> an address ID is set from PM or not. It will be used in the next two
> commits.
>
> Signed-off-by: Geliang Tang <tanggeliang@kylinos.cn>
Hi Geliang -
In cases like this where a new helper is added (and does not replace
existing open coded sections), I think it's better to have a single patch
that both adds the helper and the call to it.
Please squash patches 1 & 2.
- Mat
> ---
> net/mptcp/pm.c | 12 ++++++++++++
> net/mptcp/protocol.h | 2 ++
> 2 files changed, 14 insertions(+)
>
> diff --git a/net/mptcp/pm.c b/net/mptcp/pm.c
> index 4ae19113b8eb..6856d10368be 100644
> --- a/net/mptcp/pm.c
> +++ b/net/mptcp/pm.c
> @@ -533,6 +533,18 @@ void mptcp_pm_data_reset(struct mptcp_sock *msk)
> bitmap_fill(msk->pm.id_avail_bitmap, MPTCP_PM_MAX_ADDR_ID + 1);
> }
>
> +bool mptcp_pm_has_addr_attr_id(const struct nlattr *attr,
> + struct genl_info *info)
> +{
> + struct nlattr *tb[MPTCP_PM_ADDR_ATTR_MAX + 1];
> +
> + if (!nla_parse_nested_deprecated(tb, MPTCP_PM_ADDR_ATTR_MAX, attr,
> + mptcp_pm_address_nl_policy, info->extack) &&
> + tb[MPTCP_PM_ADDR_ATTR_ID])
> + return true;
> + return false;
> +}
> +
> void mptcp_pm_data_init(struct mptcp_sock *msk)
> {
> spin_lock_init(&msk->pm.lock);
> diff --git a/net/mptcp/protocol.h b/net/mptcp/protocol.h
> index d442d876f465..0d634e01c47d 100644
> --- a/net/mptcp/protocol.h
> +++ b/net/mptcp/protocol.h
> @@ -887,6 +887,8 @@ int mptcp_pm_parse_addr(struct nlattr *attr, struct genl_info *info,
> int mptcp_pm_parse_entry(struct nlattr *attr, struct genl_info *info,
> bool require_family,
> struct mptcp_pm_addr_entry *entry);
> +bool mptcp_pm_has_addr_attr_id(const struct nlattr *attr,
> + struct genl_info *info);
> bool mptcp_pm_addr_families_match(const struct sock *sk,
> const struct mptcp_addr_info *loc,
> const struct mptcp_addr_info *rem);
> --
> 2.40.1
>
>
>
next prev parent reply other threads:[~2024-01-31 2:15 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 6:11 [PATCH mptcp-next v10 00/23] dump for userspace pm Geliang Tang
2024-01-18 6:11 ` [PATCH mptcp-next v10 01/23] mptcp: add pm_has_addr_attr_id helper Geliang Tang
2024-01-31 2:15 ` Mat Martineau [this message]
2024-01-18 6:11 ` [PATCH mptcp-next v10 02/23] mptcp: add needs_id for userspace appending addr Geliang Tang
2024-01-31 2:20 ` Mat Martineau
2024-01-18 6:11 ` [PATCH mptcp-next v10 03/23] mptcp: add needs_id for netlink " Geliang Tang
2024-01-18 6:11 ` [PATCH mptcp-next v10 04/23] mptcp: map v4 address to v6 when destroying subflow Geliang Tang
2024-01-31 2:21 ` Mat Martineau
2024-01-18 6:11 ` [PATCH mptcp-next v10 05/23] selftests: mptcp: rm subflow with v4/v4mapped addr Geliang Tang
2024-01-18 6:11 ` [PATCH mptcp-next v10 06/23] mptcp: export mptcp_genl_family & mptcp_nl_fill_addr Geliang Tang
2024-01-18 6:11 ` [PATCH mptcp-next v10 07/23] mptcp: implement mptcp_userspace_pm_dump_addr Geliang Tang
2024-01-18 6:11 ` [PATCH mptcp-next v10 08/23] mptcp: add token for get-addr in yaml Geliang Tang
2024-01-18 6:11 ` [PATCH mptcp-next v10 09/23] mptcp: dump addrs in userspace pm list Geliang Tang
2024-01-18 6:11 ` [PATCH mptcp-next v10 10/23] mptcp: check userspace pm subflow flag Geliang Tang
2024-01-31 2:28 ` Mat Martineau
2024-02-06 2:57 ` Geliang Tang
2024-02-08 9:27 ` Matthieu Baerts
2024-01-18 6:11 ` [PATCH mptcp-next v10 11/23] selftests: mptcp: add " Geliang Tang
2024-01-18 6:11 ` [PATCH mptcp-next v10 12/23] selftests: mptcp: add token for dump_addr Geliang Tang
2024-01-18 6:11 ` [PATCH mptcp-next v10 13/23] selftests: mptcp: add check_output helper Geliang Tang
2024-01-18 6:11 ` [PATCH mptcp-next v10 14/23] selftests: mptcp: dump after creating id 0 subflow Geliang Tang
2024-01-18 6:11 ` [PATCH mptcp-next v10 15/23] selftests: mptcp: dump userspace addrs list Geliang Tang
2024-01-18 6:11 ` [PATCH mptcp-next v10 16/23] mptcp: add userspace_pm_lookup_addr_by_id helper Geliang Tang
2024-01-18 6:11 ` [PATCH mptcp-next v10 17/23] mptcp: implement mptcp_userspace_pm_get_addr Geliang Tang
2024-01-18 6:11 ` [PATCH mptcp-next v10 18/23] mptcp: get addr in userspace pm list Geliang Tang
2024-01-18 6:11 ` [PATCH mptcp-next v10 19/23] selftests: mptcp: add token for get_addr Geliang Tang
2024-01-18 6:12 ` [PATCH mptcp-next v10 20/23] selftests: mptcp: userspace pm get addr tests Geliang Tang
2024-01-18 6:12 ` [PATCH mptcp-next v10 21/23] mptcp: update set_flags interfaces Geliang Tang
2024-01-18 6:12 ` [PATCH mptcp-next v10 22/23] mptcp: set error messages for set_flags Geliang Tang
2024-01-18 6:12 ` [PATCH mptcp-next v10 23/23] selftests: mptcp: flush userspace addrs list Geliang Tang
2024-01-18 7:24 ` selftests: mptcp: flush userspace addrs list: Tests Results MPTCP CI
2024-01-18 8:03 ` MPTCP CI
2024-01-31 1:32 ` [PATCH mptcp-next v10 00/23] dump for userspace pm Mat Martineau
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=a4e54887-1155-26af-c8e1-9f4f28ca2be7@kernel.org \
--to=martineau@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