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-next v2] bpf: Update verification logic for LSM programs
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <160469769850.21746.734806332257716938.git-patchwork-notify@kernel.org>
Date:   Fri, 06 Nov 2020 21:21:38 +0000
References: <20201105230651.2621917-1-kpsingh@chromium.org>
In-Reply-To: <20201105230651.2621917-1-kpsingh@chromium.org>
To:     KP Singh <kpsingh@chromium.org>
Cc:     linux-kernel@vger.kernel.org, bpf@vger.kernel.org, ast@kernel.org,
        daniel@iogearbox.net
Precedence: bulk

Hello:

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

On Thu,  5 Nov 2020 23:06:51 +0000 you wrote:
> From: KP Singh <kpsingh@google.com>
> 
> The current logic checks if the name of the BTF type passed in
> attach_btf_id starts with "bpf_lsm_", this is not sufficient as it also
> allows attachment to non-LSM hooks like the very function that performs
> this check, i.e. bpf_lsm_verify_prog.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v2] bpf: Update verification logic for LSM programs
    https://git.kernel.org/bpf/bpf/c/6f64e4778300

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