Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH v2 bpf-next] bpf: add ambient BPF runtime context stored in
 current
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <162646364436.14878.13764135374807267506.git-patchwork-notify@kernel.org>
Date:   Fri, 16 Jul 2021 19:27:24 +0000
References: <20210712230615.3525979-1-andrii@kernel.org>
In-Reply-To: <20210712230615.3525979-1-andrii@kernel.org>
To:     Andrii Nakryiko <andrii@kernel.org>
Cc:     bpf@vger.kernel.org, netdev@vger.kernel.org, ast@fb.com,
        daniel@iogearbox.net, linux-kernel@vger.kernel.org,
        kernel-team@fb.com, yhs@fb.com
Precedence: bulk

Hello:

This patch was applied to bpf/bpf-next.git (refs/heads/master):

On Mon, 12 Jul 2021 16:06:15 -0700 you wrote:
> b910eaaaa4b8 ("bpf: Fix NULL pointer dereference in bpf_get_local_storage()
> helper") fixed the problem with cgroup-local storage use in BPF by
> pre-allocating per-CPU array of 8 cgroup storage pointers to accommodate
> possible BPF program preemptions and nested executions.
> 
> While this seems to work good in practice, it introduces new and unnecessary
> failure mode in which not all BPF programs might be executed if we fail to
> find an unused slot for cgroup storage, however unlikely it is. It might also
> not be so unlikely when/if we allow sleepable cgroup BPF programs in the
> future.
> 
> [...]

Here is the summary with links:
  - [v2,bpf-next] bpf: add ambient BPF runtime context stored in current
    https://git.kernel.org/bpf/bpf-next/c/c7603cfa04e7

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