From: Mat Martineau <martineau@kernel.org>
To: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
Cc: MPTCP Upstream <mptcp@lists.linux.dev>
Subject: Re: [PATCH mptcp-net 0/3] mptcp: pm: ignore unknown endpoint flags
Date: Wed, 26 Nov 2025 15:54:37 -0800 (PST) [thread overview]
Message-ID: <032f83ca-b331-9e4f-5739-de91b4a3ff00@kernel.org> (raw)
In-Reply-To: <20251126-mptcp-pm-kern-drop-unknown-flags-v1-0-d2e4c2ebce0c@kernel.org>
On Wed, 26 Nov 2025, Matthieu Baerts (NGI0) wrote:
> This is just a simple fix to ignore unknown endpoint flags. Recently, a
> new "laminar" flag has been added. It can be set on older kernel
> versions without effects -- which is good -- but it is strange to report
> it in the endpoints dumps if it is not supported.
>
> # uname -r
> 6.17.9
> # ip mptcp endpoint add 1.2.3.4 laminar # not supported on v6.17
> # ip mptcp endpoint
> 1.2.3.4 id 1 laminar
>
> Patch 1 fixes that, while Patch 2 validates that.
>
> Patch 3 is for mptcp-next, to correctly follow the specs and accept u32
> flags instead of u8. This doesn't change anything, but avoids
> confusions.
>
> Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
> ---
> Matthieu Baerts (NGI0) (3):
> mptcp: pm: ignore unknown endpoint flags
> selftests: mptcp: pm: ensure unknown flags are ignored
> mptcp: pm: align endpoint flags size with the NL specs
Hi Matthieu!
All three patches LGTM:
Reviewed-by: Mat Martineau <martineau@kernel.org>
See my comment on patch 2 regarding an additional fourth patch for
net-next.
Thanks,
Mat
>
> include/uapi/linux/mptcp.h | 1 +
> net/mptcp/pm_netlink.c | 3 ++-
> net/mptcp/protocol.h | 4 ++--
> tools/testing/selftests/net/mptcp/pm_netlink.sh | 4 ++++
> tools/testing/selftests/net/mptcp/pm_nl_ctl.c | 11 +++++++++++
> 5 files changed, 20 insertions(+), 3 deletions(-)
> ---
> base-commit: 690b1c68fd1e566ffa60fec98e09292cc9f04a3a
> change-id: 20251125-mptcp-pm-kern-drop-unknown-flags-e4ec71df02e7
>
> Best regards,
> --
> Matthieu Baerts (NGI0) <matttbe@kernel.org>
>
>
>
next prev parent reply other threads:[~2025-11-26 23:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 18:31 [PATCH mptcp-net 0/3] mptcp: pm: ignore unknown endpoint flags Matthieu Baerts (NGI0)
2025-11-26 18:31 ` [PATCH mptcp-net 1/3] " Matthieu Baerts (NGI0)
2025-11-26 18:31 ` [PATCH mptcp-net 2/3] selftests: mptcp: pm: ensure unknown flags are ignored Matthieu Baerts (NGI0)
2025-11-26 23:57 ` Mat Martineau
2025-11-27 14:57 ` Matthieu Baerts
2025-11-26 18:31 ` [PATCH mptcp-net 3/3] mptcp: pm: align endpoint flags size with the NL specs Matthieu Baerts (NGI0)
2025-11-26 19:52 ` [PATCH mptcp-net 0/3] mptcp: pm: ignore unknown endpoint flags MPTCP CI
2025-11-26 23:54 ` Mat Martineau [this message]
2025-11-27 15:07 ` Matthieu Baerts
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=032f83ca-b331-9e4f-5739-de91b4a3ff00@kernel.org \
--to=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
/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