Re: [PATCH v5 2/3] bpf: add bpf_init_inode_xattr kfunc for atomic inode labeling
David Windsor <[email protected]> Mon, 20 Jul 2026 14:12:06 -0400
| Newsgroups | org.kernel.vger.linux-integrity,org.kernel.vger.bpf,org.kernel.vger.linux-fsdevel,org.kernel.vger.linux-kernel,org.kernel.vger.linux-kselftest,org.kernel.vger.linux-security-module,org.kernel.vger.selinux |
|---|---|
| Message-ID | <CAEXv5_gt7BPWvdR4D1_3XJ0_XpBXWN52jeAOf1K2QJ7LL6CtPQ@mail.gmail.com> |
On Thu, Jul 16, 2026 at 5:55=E2=80=AFPM Paul Moore <[email protected]> wr= ote: > > > I'm sorry David, now that I'm seeing this function again, especially > with the LSM specific bits extracted into a LSM function, this absolutely > belongs somewhere under security/. It's only callable from within a > BPF LSM callback and all it does outside of some BPF pointer boilerplate > is call right back into a LSM helper function. > > If the BPF maintainers aren't willing to accept that, then we will all > need to find another way. > Where this code lands doesn't matter to me, so I'll stay out of the decision of where it lives. If this kfunc goes to security/, would we also want to move eg bpf_set_dentry_xattr similarly? I'll roll v6 of this series meanwhile and we'll see what the BPF maintainers say.