Re: [PATCH v6 bpf-next 3/4] bpf: add bpf_init_inode_xattr kfunc for atomic inode labeling
David Windsor <[email protected]> Thu, 30 Jul 2026 20:01:00 -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_iiNspub=qE1YW-01sV_bxxFUrrcAR4KV4Ec5i_mePtHw@mail.gmail.com> |
On Thu, Jul 30, 2026 at 7:53=E2=80=AFPM Paul Moore <[email protected]> wr= ote: > > Based on our discussion in the v5 patchset, I was expecting to see > this under security/; did something happen, or was there some > confusion? > Nothing happened, perhaps some confusion. I was basing the placement off of Kumar's comment in v5: > I don't think we should do that in v6 though. What you're describing affe= cts all other xattr kfuncs. That's a broader discussion we should have separately w= hen folks are back from vacation, and more importantly involve FS folks where t= he code currently lives. As you say yourself, the lines are blurry, xattrs are= as much a filesystem concept. My take on this was, leave it in fs/ for now and then litigate the placement of all of the fs-related kfuncs after bpf_init_inode_xattr lands. Happy to place this in security/ in v7, if that's preferred. Apologies if I misread the thread. -David > -- > paul-moore.com