[PATCH bpf-next v2 0/3] BPF signature hash chains
Paul Moore
paul at paul-moore.com
Thu Oct 9 20:47:13 UTC 2025
On Tue, Oct 7, 2025 at 9:53 AM KP Singh <kpsingh at kernel.org> wrote:
> On Mon, Oct 6, 2025 at 5:08 AM Paul Moore <paul at paul-moore.com> wrote:
> > On Fri, Oct 3, 2025 at 12:25 PM KP Singh <kpsingh at kernel.org> wrote:
> > > On Fri, Oct 3, 2025 at 4:36 AM Paul Moore <paul at paul-moore.com> wrote:
> > > > On Thu, Oct 2, 2025 at 9:48 AM KP Singh <kpsingh at kernel.org> wrote:
> > > > > On Wed, Oct 1, 2025 at 11:37 PM Paul Moore <paul at paul-moore.com> wrote:
...
> I feel we will keep going in circles on this and I will leave it up to
> the maintainers to resolve this.
Yes, I think we can all agree that the discussion has reached a point
where both sides are simply repeating ourselves.
I believe we've outlined why the code merged into Linus' tree during
this merge window does not meet the BPF signature verification
requirements of a number of different user groups, with Blaise
proposing an addition to KP's code to satisfy those needs. Further, I
believe that either Blaise, James, or I have responded to all of KP's
concerns regarding Blaise's patchset, and while KP may not be happy
with those answers, no one has yet to offer an alternative solution to
Blaise's patchset.
With that in mind, I agree with KP that it's time for "the maintainers
to resolve this". Alexei, will you be merging Blaise's patchset and
sending it up to Linus?
--
paul-moore.com
More information about the Linux-security-module-archive
mailing list