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
| ||
|
Date: Fri, 06 Nov 2020 04:10:04 +0000 From: patchwork-bot+netdevbpf@...nel.org To: David Verbeiren <david.verbeiren@...sares.net> Cc: bpf@...r.kernel.org, andrii@...nel.org, netdev@...r.kernel.org, matthieu.baerts@...sares.net Subject: Re: [PATCH bpf v4] bpf: zero-fill re-used per-cpu map element Hello: This patch was applied to bpf/bpf.git (refs/heads/master): On Wed, 4 Nov 2020 12:23:32 +0100 you wrote: > Zero-fill element values for all other cpus than current, just as > when not using prealloc. This is the only way the bpf program can > ensure known initial values for all cpus ('onallcpus' cannot be > set when coming from the bpf program). > > The scenario is: bpf program inserts some elements in a per-cpu > map, then deletes some (or userspace does). When later adding > new elements using bpf_map_update_elem(), the bpf program can > only set the value of the new elements for the current cpu. > When prealloc is enabled, previously deleted elements are re-used. > Without the fix, values for other cpus remain whatever they were > when the re-used entry was previously freed. > > [...] Here is the summary with links: - [bpf,v4] bpf: zero-fill re-used per-cpu map element https://git.kernel.org/bpf/bpf/c/d3bec0138bfb 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