From: Matthieu Baerts <matttbe@kernel.org>
To: Andrea Claudi <aclaudi@redhat.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: David Ahern <dsahern@kernel.org>,
netdev@vger.kernel.org, MPTCP Linux <mptcp@lists.linux.dev>
Subject: Re: [PATCH iproute2-next] mptcp: add implicit flag to the 'ip mptcp' inline help
Date: Wed, 22 Oct 2025 16:49:41 +0200 [thread overview]
Message-ID: <946ceea8-eb58-4140-aa5a-94605cd697ce@kernel.org> (raw)
In-Reply-To: <0a81085b8be2bee69cf217d2379e87730c28b1c1.1761074697.git.aclaudi@redhat.com>
Hi Andrea,
Sorry, I'm reacting a bit too late here (but Stephen applied the patch
very quickly :) ).
On 21/10/2025 21:26, Andrea Claudi wrote:
> ip mptcp supports the implicit flag since commit 3a2535a41854 ("mptcp:
> add support for implicit flag"), however this flag is not listed in the
> command inline help.
>
> Add the implicit flag to the inline help.
I would rather not: as written in the man page (by you in the mentioned
commit :) ) "Implicit endpoints cannot be created from user-space". Such
endpoints can be created by the MPTCP in-kernel path-manager in some
circumstances, but if the user-space cannot set the flag, then probably
better not to add it in the command inline help, no?
If someone tries to create an "implicit" endpoint, the kernel will
reject this request, see:
https://elixir.bootlin.com/linux/v6.17/source/net/mptcp/pm_kernel.c#L813
I can send a revert. I have other small changes to send.
@Stephen: while at it, would it be OK if I also add an entry for files
linked related to MPTCP in the MAINTAINERS file?
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2025-10-22 14:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 19:26 [PATCH iproute2-next] mptcp: add implicit flag to the 'ip mptcp' inline help Andrea Claudi
2025-10-21 20:53 ` Stephen Hemminger
2025-10-21 22:10 ` patchwork-bot+netdevbpf
2025-10-22 14:49 ` Matthieu Baerts [this message]
2025-10-22 15:03 ` David Ahern
2025-10-22 17:06 ` Stephen Hemminger
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=946ceea8-eb58-4140-aa5a-94605cd697ce@kernel.org \
--to=matttbe@kernel.org \
--cc=aclaudi@redhat.com \
--cc=dsahern@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/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;
as well as URLs for NNTP newsgroup(s).