Skip to contentSkip to conversation

bpf: Update bpf_design_QA.rst to clarify that attaching to functions is not ABI

PATCH New Paul E. McKenney 1 participant 1 message Aug 2, 2022

Subsystems (4)
lore
Share & tools
lore
#0 lore raw

PATCH v3 2/3 bpf: Update bpf_design_QA.rst to clarify that attaching to functions is not ABI

This patch updates bpf_design_QA.rst to clarify that the ability to attach a BPF program to an arbitrary function in the kernel does not make that function become part of the Linux kernel's ABI.

[ paulmck: Apply Daniel Borkmann feedback. ]

---
 Documentation/bpf/bpf_design_QA.rst | 12 ++++++++++++
 1 file changed, 12 insertions(+)
Documentation/bpf/bpf_design_QA.rst +12 -0
index 2ed9128cfbec8..a06ae8a828e3d 100644
@@ -279,3 +279,15 @@ cc (congestion-control) implementations.  If any of these kernel
 functions has changed, both the in-tree and out-of-tree kernel tcp cc
 implementations have to be changed.  The same goes for the bpf
 programs and they have to be adjusted accordingly.
+
+Q: Attaching to arbitrary kernel functions is an ABI?
+-----------------------------------------------------
+Q: BPF programs can be attached to many kernel functions.  Do these
+kernel functions become part of the ABI?
+
+A: NO.
+
+The kernel function prototypes will change, and BPF programs attaching to
+them will need to change.  The BPF compile-once-run-everywhere (CO-RE)
+should be used in order to make it easier to adapt your BPF programs to
+different versions of the kernel.
Signature · 1 line
2.31.1.189.g2e36527f23