netdev - Re: [PATCH net-next] tcp: only release congestion control if it has been initialized

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: 
 <173042523201.2147711.1857098885103384242.git-patchwork-notify@kernel.org>
Date: Fri, 01 Nov 2024 01:40:32 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Pengcheng Yang <yangpc@...gsu.com>
Cc: edumazet@...gle.com, ncardwell@...gle.com, davem@...emloft.net,
 dsahern@...nel.org, kuba@...nel.org, pabeni@...hat.com,
 netdev@...r.kernel.org
Subject: Re: [PATCH net-next] tcp: only release congestion control if it has been
 initialized

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:

On Fri, 25 Oct 2024 16:45:44 +0800 you wrote:
> Currently, when cleaning up congestion control, we always call the
> release regardless of whether it has been initialized. There is no
> need to release when closing TCP_LISTEN and TCP_CLOSE (close
> immediately after socket()).
> 
> In this case, tcp_cdg calls kfree(NULL) in release without causing
> an exception, but for some customized ca, this could lead to
> unexpected exceptions. We need to ensure that init and release are
> called in pairs.
> 
> [...]

Here is the summary with links:
  - [net-next] tcp: only release congestion control if it has been initialized
    https://git.kernel.org/netdev/net-next/c/cf44bd08cdee

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