Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH v2] libbpf: fix BPF_MAP_TYPE_PERF_EVENT_ARRAY auto-pinning
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <164606640987.23345.3964294221213220765.git-patchwork-notify@kernel.org>
Date:   Mon, 28 Feb 2022 16:40:09 +0000
References: <20220225152355.315204-1-stijn@linux-ipv6.be>
In-Reply-To: <20220225152355.315204-1-stijn@linux-ipv6.be>
To:     Stijn Tintel <stijn@linux-ipv6.be>
Cc:     bpf@vger.kernel.org, songliubraving@fb.com, andrii@kernel.org,
        toke@redhat.com, netdev@vger.kernel.org,
        linux-kernel@vger.kernel.org, kpsingh@kernel.org, yhs@fb.com,
        kafai@fb.com, daniel@iogearbox.net, ast@kernel.org
Precedence: bulk

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.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