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 bpf-next v2] bpf: Cache the last valid build_id.
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <164606880999.12943.12753138670419777830.git-patchwork-notify@kernel.org>
Date:   Mon, 28 Feb 2022 17:20:09 +0000
References: <20220224000531.1265030-1-haoluo@google.com>
In-Reply-To: <20220224000531.1265030-1-haoluo@google.com>
To:     Hao Luo <haoluo@google.com>
Cc:     ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
        songliubraving@fb.com, namhyung@kernel.org, blakejones@google.com,
        bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
        gthelen@google.com
Precedence: bulk

Hello:

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

On Wed, 23 Feb 2022 16:05:31 -0800 you wrote:
> For binaries that are statically linked, consecutive stack frames are
> likely to be in the same VMA and therefore have the same build id.
> As an optimization for this case, we can cache the previous frame's
> VMA, if the new frame has the same VMA as the previous one, reuse the
> previous one's build id. We are holding the MM locks as reader across
> the entire loop, so we don't need to worry about VMA going away.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v2] bpf: Cache the last valid build_id.
    https://git.kernel.org/bpf/bpf-next/c/ceac059ed4fd

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