netdev - Re: [PATCH v2] libbpf: fix BPF_MAP_TYPE_PERF_EVENT

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]

Date:   Mon, 28 Feb 2022 16:40:09 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Stijn Tintel <stijn@...ux-ipv6.be>
Cc:     bpf@...r.kernel.org, songliubraving@...com, andrii@...nel.org,
        toke@...hat.com, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org, kpsingh@...nel.org, yhs@...com,
        kafai@...com, daniel@...earbox.net, ast@...nel.org
Subject: Re: [PATCH v2] libbpf: fix BPF_MAP_TYPE_PERF_EVENT_ARRAY auto-pinning

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@...earbox.net>:

On Fri, 25 Feb 2022 17:23:55 +0200 you wrote:
> When a BPF map of type BPF_MAP_TYPE_PERF_EVENT_ARRAY doesn't have the
> max_entries parameter set, the map will be created with max_entries set
> to the number of available CPUs. When we try to reuse such a pinned map,
> map_is_reuse_compat will return false, as max_entries in the map
> definition differs from max_entries of the existing map, causing the
> following error:
> 
> [...]

Here is the summary with links:
  - [v2] libbpf: fix BPF_MAP_TYPE_PERF_EVENT_ARRAY auto-pinning
    https://git.kernel.org/bpf/bpf-next/c/a4fbfdd7a160

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