Re: [PATCH bpf-next 0/2] lsm: give BPF programs a way to query locked_down state

David Windsor <[email protected]>
Newsgroups org.kernel.vger.linux-security-module,org.kernel.vger.bpf,org.kernel.vger.linux-kernel
Message-ID <CAEXv5_j0h+qCvj5U_aha_7OUUyuR6FPzufo3zK=Ax67724CPjA@mail.gmail.com>
On Tue, Aug 18, 2026 at 3:48 PM Paul Moore <[email protected]> wrote:
>
> On Tue, Aug 18, 2026 at 1:42 PM David Windsor <[email protected]> wrote:
> > On Tue, Aug 18, 2026 at 5:43 AM Kumar Kartikeya Dwivedi
> > <[email protected]> wrote:
> > >
> > >
> > > Lastly, given the difficulties we've faced from the LSM maintainers, I'm not
> > > inclined to waste more time in explaining again why this cannot go under
> > > security/.
> > >
> >
> > I'm still going to send v7 of bpf_init_inode_xattr series, even though
> > it's a stalemate. Haven't yet decided where it'll live in v7, I'm
> > inclined to leave it where it was (in fs/) since one side will NAK it
> > wherever it lives. We can record NAKs and take it from there.
>
> As a FYI, I'm not going to ACK any of the LSM changes with the kfunc
> in security/bpf_lsm_kfuncs.c.
>

Hmm, even if it lands in security/ you'd not ACK it? I thought what
we'd settled on as acceptable from your end was placing it in
security/, then having a broader discussion about the rest of the fs
kfuncs? Just trying to understand everyone's position.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.