Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] How far to go with eBPF
Steven Rostedt <[email protected]> Thu, 16 Jun 2022 15:08:45 -0400
| Newsgroups | org.linuxfoundation.lists.ksummit-discuss,dev.linux.lists.ksummit |
|---|---|
| Message-ID | <[email protected]> |
On Thu, 16 Jun 2022 14:25:44 -0400 James Bottomley <[email protected]> wrote: > Not if it's managed correctly. One method could simply be to not care > but be careful. After all, lots of companies still manage to produce > proprietary modules even with us actively trying to break the API. > Either it's not as difficult as we think or API changes are easier to > cope with than we assume. All I read from this is that eBPF is the new way that proprietary modules can have their stable API. The problem I have here is that eBPF is becoming extremely invasive. It is now hooking to any function in the kernel that isn't marked notrace. If there's not a clear border on what is considered non-stable now, we will be fighting with those that say "hey this broke my bpf program, revert it please" for a long time coming. -- Steve _______________________________________________ Ksummit-discuss mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss