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 bpf] bpf: exempt CAP_BPF from checks against bpf_jit_limit
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <163234680674.13903.12726490005358522005.git-patchwork-notify@kernel.org>
Date:   Wed, 22 Sep 2021 21:40:06 +0000
References: <20210922111153.19843-1-lmb@cloudflare.com>
In-Reply-To: <20210922111153.19843-1-lmb@cloudflare.com>
To:     Lorenz Bauer <lmb@cloudflare.com>
Cc:     ast@kernel.org, daniel@iogearbox.net, kernel-team@cloudflare.com,
        netdev@vger.kernel.org, bpf@vger.kernel.org,
        linux-kernel@vger.kernel.org
Precedence: bulk

Hello:

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

On Wed, 22 Sep 2021 12:11:52 +0100 you wrote:
> When introducing CAP_BPF, bpf_jit_charge_modmem was not changed to
> treat programs with CAP_BPF as privileged for the purpose of JIT
> memory allocation. This means that a program without CAP_BPF can
> block a program with CAP_BPF from loading a program.
> 
> Fix this by checking bpf_capable in bpf_jit_charge_modmem.
> 
> [...]

Here is the summary with links:
  - [bpf] bpf: exempt CAP_BPF from checks against bpf_jit_limit
    https://git.kernel.org/bpf/bpf/c/7c3a00911b3d

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