[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<170173202339.29919.16182353251638504303.git-patchwork-notify@kernel.org>
Date: Mon, 04 Dec 2023 23:20:23 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Daniel Borkmann <daniel@...earbox.net>
Cc: netdev@...r.kernel.org, security@...c.gov.uk, gregkh@...uxfoundation.org,
willemdebruijn.kernel@...il.com, torvalds@...ux-foundation.org,
stable@...nel.org
Subject: Re: [PATCH net v2] packet: Move reference count in packet_sock to
atomic_long_t
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Fri, 1 Dec 2023 14:10:21 +0100 you wrote:
> In some potential instances the reference count on struct packet_sock
> could be saturated and cause overflows which gets the kernel a bit
> confused. To prevent this, move to a 64-bit atomic reference count on
> 64-bit architectures to prevent the possibility of this type to overflow.
>
> Because we can not handle saturation, using refcount_t is not possible
> in this place. Maybe someday in the future if it changes it could be
> used. Also, instead of using plain atomic64_t, use atomic_long_t instead.
> 32-bit machines tend to be memory-limited (i.e. anything that increases
> a reference uses so much memory that you can't actually get to 2**32
> references). 32-bit architectures also tend to have serious problems
> with 64-bit atomics. Hence, atomic_long_t is the more natural solution.
>
> [...]
Here is the summary with links:
- [net,v2] packet: Move reference count in packet_sock to atomic_long_t
https://git.kernel.org/netdev/net/c/db3fadacaf0c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists