MPTCP Linux Development
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: Andrea Claudi <aclaudi@redhat.com>,
	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 10:06:52 -0700	[thread overview]
Message-ID: <20251022100652.6d24c0fe@phoenix.lan> (raw)
In-Reply-To: <946ceea8-eb58-4140-aa5a-94605cd697ce@kernel.org>

On Wed, 22 Oct 2025 16:49:41 +0200
Matthieu Baerts <matttbe@kernel.org> wrote:

> 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.

Thanks I reverted it

      parent reply	other threads:[~2025-10-22 17:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0a81085b8be2bee69cf217d2379e87730c28b1c1.1761074697.git.aclaudi@redhat.com>
2025-10-22 14:49 ` [PATCH iproute2-next] mptcp: add implicit flag to the 'ip mptcp' inline help Matthieu Baerts
2025-10-22 15:03   ` David Ahern
2025-10-22 17:06   ` Stephen Hemminger [this message]

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=20251022100652.6d24c0fe@phoenix.lan \
    --to=stephen@networkplumber.org \
    --cc=aclaudi@redhat.com \
    --cc=dsahern@kernel.org \
    --cc=matttbe@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=netdev@vger.kernel.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