Received-SPF: pass (google.com: domain of linux-kernel+bounces-174560-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
Content-Type: text/plain; charset="utf-8"
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCHv2] l2tp: Support several sockets with same IP/port quadruple
From: patchwork-bot+netdevbpf@kernel.org
Message-Id: 
 <171526322793.14863.3674169086267452877.git-patchwork-notify@kernel.org>
Date: Thu, 09 May 2024 14:00:27 +0000
References: <20240506215336.1470009-1-samuel.thibault@ens-lyon.org>
In-Reply-To: <20240506215336.1470009-1-samuel.thibault@ens-lyon.org>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>
Cc: tparkin@katalix.com, edumazet@google.com, kuba@kernel.org,
 pabeni@redhat.com, jchapman@katalix.com, linux-kernel@vger.kernel.org,
 netdev@vger.kernel.org

Hello:

This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Mon,  6 May 2024 23:53:35 +0200 you wrote:
> Some l2tp providers will use 1701 as origin port and open several
> tunnels for the same origin and target. On the Linux side, this
> may mean opening several sockets, but then trafic will go to only
> one of them, losing the trafic for the tunnel of the other socket
> (or leaving it up to userland, consuming a lot of cpu%).
> 
> This can also happen when the l2tp provider uses a cluster, and
> load-balancing happens to migrate from one origin IP to another one,
> for which a socket was already established. Managing reassigning
> tunnels from one socket to another would be very hairy for userland.
> 
> [...]

Here is the summary with links:
  - [PATCHv2] l2tp: Support several sockets with same IP/port quadruple
    https://git.kernel.org/netdev/net-next/c/628bc3e5a1be

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html