Re: [PATCH v6 bpf-next 3/4] bpf: add bpf_init_inode_xattr kfunc for atomic inode labeling
Paul Moore <[email protected]> Fri, 31 Jul 2026 18:23:01 -0400
| Newsgroups | org.kernel.vger.linux-fsdevel,org.kernel.vger.bpf,org.kernel.vger.linux-integrity,org.kernel.vger.linux-kernel,org.kernel.vger.linux-kselftest,org.kernel.vger.linux-security-module,org.kernel.vger.selinux |
|---|---|
| Message-ID | <CAHC9VhQmb=v3-T5HZUzfr_me6S7bo6sX0Vs4nDFQZnMe+SQOMQ@mail.gmail.com> |
On Fri, Jul 31, 2026 at 6:04 PM Kumar Kartikeya Dwivedi <[email protected]> wrote: > On Fri Jul 31, 2026 at 11:49 PM CEST, Paul Moore wrote: > > On Fri, Jul 31, 2026 at 5:29 PM Kumar Kartikeya Dwivedi > > <[email protected]> wrote: > >> On Fri Jul 31, 2026 at 10:48 PM CEST, Paul Moore wrote: > >> > On Fri, Jul 31, 2026 at 4:16 PM Kumar Kartikeya Dwivedi > >> > <[email protected]> wrote: > >> >> On Fri Jul 31, 2026 at 10:01 PM CEST, Paul Moore wrote: > >> >> > On Fri, Jul 31, 2026 at 3:20 PM Kumar Kartikeya Dwivedi > >> >> > <[email protected]> wrote: > >> >> >> On Fri Jul 31, 2026 at 9:05 PM CEST, Paul Moore wrote: > >> >> >> > On Fri, Jul 31, 2026 at 2:50 PM Kumar Kartikeya Dwivedi > >> >> >> > <[email protected]> wrote: > >> >> >> >> On Fri Jul 31, 2026 at 8:42 PM CEST, Paul Moore wrote: > >> >> >> >> > On Fri, Jul 31, 2026 at 2:18 PM Kumar Kartikeya Dwivedi > >> >> >> >> > <[email protected]> wrote: > >> >> >> >> >> On Fri Jul 31, 2026 at 6:59 PM CEST, Paul Moore wrote: > >> >> >> >> >> > On Fri, Jul 31, 2026 at 12:32 PM Kumar Kartikeya Dwivedi > >> >> >> >> >> > <[email protected]> wrote: > >> >> >> >> >> >> On Fri Jul 31, 2026 at 6:02 PM CEST, Paul Moore wrote: > >> >> >> >> >> >> > On Fri, Jul 31, 2026 at 11:44 AM Kumar Kartikeya Dwivedi > >> >> >> >> >> >> > <[email protected]> wrote: > >> >> >> >> >> >> >> On Fri Jul 31, 2026 at 5:30 PM CEST, David Windsor wrote: > >> >> >> >> >> >> >> > On Fri, Jul 31, 2026 at 11:17 AM Paul Moore <[email protected]> wrote: ... > As a consequence, everyone suffers because they first need to satisfy your whims > on how all code and kfuncs written thus far are wrong, and need to be moved > around ASAP, including the one being proposed. That's not a reasonble or truthful summary of things, I've only requested that David locate his proposed kfunc in security/bpf_lsm_kfuncs.c, I never suggested he move any others. -- paul-moore.com