Re: [BUG] bpf, lsm: new first argument in 7.4 inode hooks silently breaks BPF LSMs

From: Paul Moore

Date: Thu Nov 19 2026 - 14:38:04 EST


On Thu, Nov 19, 2026 at 12:59 PM Andrii Nakryiko
<andrii.nakryiko@xxxxxxxxx> wrote:
> On Wed, Nov 18, 2026 at 7:14 AM Paul Mabileau
> <paul.mabileau@xxxxxxxxxxxxx> wrote:
> >
> > Hello,
> >
> > On our end, we also have already merged code to adapt our eBPFs to the argument order change. However, we would still prefer if this easily-avoidable breakage could be fixed by moving the argument to the end, even if it means having to revert our fix.
> >
> > This is motivated by the fact that such a change is not made in place on our end because we ship our software to environments we don't control, meaning that any and potentially all versions ranging from 4.11 to the very latest should be supported, so the change is made by compiling and shipping a new variant of the concerned eBPFs for the version interval it is valid for (7.4+ in this case). And that has to be done every time there is an upstream change like this, so the total installation size and overall complexity grows accordingly.
> >
> > If we could avoid that, especially for such trivial root causes, it would be nice.
> >
>
> I agree, and that's why I'm asking Paul to accept the patch reordering
> the newly added argument before 7.4 final is released.
>
> I do not think that the maintainer's personal preference for argument
> ordering beats real user pain.

As stated several times in the past, the problem lies not with the LSM
framework but with the lack of an abstraction layer in the BPF LSM
providing a stable API. As far as I can tell the lack of an
abstraction layer in the BPF LSM is by design, and while that does
provide some advantages, one of the notable disadvantages is that the
API is unstable. If you want to be upset at anyone, direct your
frustrations towards the design and current implementation of the BPF
LSM.

--
paul-moore.com