MPTCP Linux Development
 help / color / mirror / Atom feed
* Re: FAILED: patch "[PATCH] mptcp: pm: check add_addr_accept_max before accepting new" failed to apply to 5.10-stable tree
       [not found] <2024082609-vivacious-jaywalker-cfac@gregkh>
@ 2024-09-06  9:00 ` Matthieu Baerts
  0 siblings, 0 replies; only message in thread
From: Matthieu Baerts @ 2024-09-06  9:00 UTC (permalink / raw)
  To: gregkh, kuba, martineau; +Cc: stable, MPTCP Linux

Hi Greg,

On 26/08/2024 14:07, gregkh@linuxfoundation.org wrote:
> 
> The patch below does not apply to the 5.10-stable tree.
> If someone wants it applied there, or to any other stable or longterm
> tree, then please email the backport, including the original git commit
> id to <stable@vger.kernel.org>.

Thank you for the notification!

(...)

> ------------------ original commit in Linus's tree ------------------
> 
> From 0137a3c7c2ea3f9df8ebfc65d78b4ba712a187bb Mon Sep 17 00:00:00 2001
> From: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
> Date: Mon, 19 Aug 2024 21:45:28 +0200
> Subject: [PATCH] mptcp: pm: check add_addr_accept_max before accepting new
>  ADD_ADDR
> 
> The limits might have changed in between, it is best to check them
> before accepting new ADD_ADDR.
> 
> Fixes: d0876b2284cf ("mptcp: add the incoming RM_ADDR support")

The code is too different in v5.10, and I don't think it is worth it to
have this small fix in v5.10.

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2024-09-06  9:00 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <2024082609-vivacious-jaywalker-cfac@gregkh>
2024-09-06  9:00 ` FAILED: patch "[PATCH] mptcp: pm: check add_addr_accept_max before accepting new" failed to apply to 5.10-stable tree Matthieu Baerts

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox