netdev - Re: [PATCH net] net: fix sk_memory_allocated

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: 
 <171392522807.21916.18094372722686134679.git-patchwork-notify@kernel.org>
Date: Wed, 24 Apr 2024 02:20:28 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Eric Dumazet <edumazet@...gle.com>
Cc: davem@...emloft.net, kuba@...nel.org, pabeni@...hat.com,
 netdev@...r.kernel.org, willemb@...gle.com, ncardwell@...gle.com,
 eric.dumazet@...il.com, jonathan.heathcote@....co.uk, soheil@...gle.com
Subject: Re: [PATCH net] net: fix sk_memory_allocated_{add|sub} vs softirqs

Hello:

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

On Sun, 21 Apr 2024 17:52:48 +0000 you wrote:
> Jonathan Heathcote reported a regression caused by blamed commit
> on aarch64 architecture.
> 
> x86 happens to have irq-safe __this_cpu_add_return()
> and __this_cpu_sub(), but this is not generic.
> 
> I think my confusion came from "struct sock" argument,
> because these helpers are called with a locked socket.
> But the memory accounting is per-proto (and per-cpu after
> the blamed commit). We might cleanup these helpers later
> to directly accept a "struct proto *proto" argument.
> 
> [...]

Here is the summary with links:
  - [net] net: fix sk_memory_allocated_{add|sub} vs softirqs
    https://git.kernel.org/netdev/net/c/3584718cf2ec

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