mptcp.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
To: mptcp@lists.linux.dev
Cc: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>,
	 Thomas Dreibholz <dreibh@simula.no>
Subject: [PATCH mptcp-net 0/2] mptcp: pm: kernel: flush: do not reset ADD_ADDR limit
Date: Wed, 06 Aug 2025 16:22:05 +0200	[thread overview]
Message-ID: <20250806-mptcp-pm-flush-limit-v1-0-9f83699e0863@kernel.org> (raw)

A flush of the MPTCP endpoints should not affect the MPTCP limits. In
other words, 'ip mptcp endpoint flush' should not change 'ip mptcp
limits'.

But it was the case. Patch 1 fixes the issue, and Patch 2 modified
pm_netlink.sh selftest to validate the modification on the kernel side.

Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
---
Matthieu Baerts (NGI0) (2):
      mptcp: pm: kernel: flush: do not reset ADD_ADDR limit
      selftests: mptcp: pm: check flush doesn't reset limits

 net/mptcp/pm_kernel.c                           | 1 -
 tools/testing/selftests/net/mptcp/pm_netlink.sh | 1 +
 2 files changed, 1 insertion(+), 1 deletion(-)
---
base-commit: 8353c34f924e5fb87e86e5587e15df160add9a44
change-id: 20250806-mptcp-pm-flush-limit-c5a2d74fc2ea

Best regards,
-- 
Matthieu Baerts (NGI0) <matttbe@kernel.org>


             reply	other threads:[~2025-08-06 14:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-06 14:22 Matthieu Baerts (NGI0) [this message]
2025-08-06 14:22 ` [PATCH mptcp-net 1/2] mptcp: pm: kernel: flush: do not reset ADD_ADDR limit Matthieu Baerts (NGI0)
2025-08-06 14:22 ` [PATCH mptcp-net 2/2] selftests: mptcp: pm: check flush doesn't reset limits Matthieu Baerts (NGI0)
2025-08-06 16:02 ` [PATCH mptcp-net 0/2] mptcp: pm: kernel: flush: do not reset ADD_ADDR limit MPTCP CI
2025-08-14  0:25 ` Mat Martineau
2025-08-15 11:00   ` 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=20250806-mptcp-pm-flush-limit-v1-0-9f83699e0863@kernel.org \
    --to=matttbe@kernel.org \
    --cc=dreibh@simula.no \
    --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;
as well as URLs for NNTP newsgroup(s).