netdev - Re: [PATCH net-next] l2tp: fix l2tp_session_register with colliding l2tpv3 IDs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: 
 <172075383064.14429.18140560465588954421.git-patchwork-notify@kernel.org>
Date: Fri, 12 Jul 2024 03:10:30 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: James Chapman <jchapman@...alix.com>
Cc: netdev@...r.kernel.org, davem@...emloft.net, edumazet@...gle.com,
 kuba@...nel.org, pabeni@...hat.com, tparkin@...alix.com,
 samuel.thibault@...-lyon.org, ridge.kennedy@...iedtelesis.co.nz,
 thorsten.blum@...lux.com
Subject: Re: [PATCH net-next] l2tp: fix l2tp_session_register with colliding
 l2tpv3 IDs

Hello:

This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@...emloft.net>:

On Tue,  9 Jul 2024 17:28:39 +0100 you wrote:
> When handling colliding L2TPv3 session IDs, we use the existing
> session IDR entry and link the new session on that using
> session->coll_list. However, when using an existing IDR entry, we must
> not do the idr_replace step.
> 
> Fixes: aa5e17e1f5ec ("l2tp: store l2tpv3 sessions in per-net IDR")
> Signed-off-by: James Chapman <jchapman@...alix.com>
> Signed-off-by: Tom Parkin <tparkin@...alix.com>
> 
> [...]

Here is the summary with links:
  - [net-next] l2tp: fix l2tp_session_register with colliding l2tpv3 IDs
    https://git.kernel.org/netdev/net-next/c/2146b7dd354c

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