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] bpf: add config to allow loading modules with BTF
 mismatches
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <164605505797.13902.1254314206143134404.git-patchwork-notify@kernel.org>
Date:   Mon, 28 Feb 2022 13:30:57 +0000
References: <20220223012814.1898677-1-connoro@google.com>
In-Reply-To: <20220223012814.1898677-1-connoro@google.com>
To:     Connor O'Brien <connoro@google.com>
Cc:     ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
        kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
        john.fastabend@gmail.com, kpsingh@kernel.org,
        shung-hsi.yu@suse.com, netdev@vger.kernel.org, bpf@vger.kernel.org,
        linux-kernel@vger.kernel.org, msuchanek@suse.de
Precedence: bulk

Hello:

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

On Wed, 23 Feb 2022 01:28:14 +0000 you wrote:
> BTF mismatch can occur for a separately-built module even when the ABI
> is otherwise compatible and nothing else would prevent successfully
> loading. Add a new config to control how mismatches are handled. By
> default, preserve the current behavior of refusing to load the
> module. If MODULE_ALLOW_BTF_MISMATCH is enabled, load the module but
> ignore its BTF information.
> 
> [...]

Here is the summary with links:
  - [bpf-next] bpf: add config to allow loading modules with BTF mismatches
    https://git.kernel.org/bpf/bpf-next/c/5e214f2e43e4

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