Skip to contentSkip to conversation

bpf: Update bpf_design_QA.rst to clarify that kprobes 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 1/3 bpf: Update bpf_design_QA.rst to clarify that kprobes is not ABI

This patch updates bpf_design_QA.rst to clarify that the ability to attach a BPF program to a given point in the kernel code via kprobes does not make that attachment point be part of the Linux kernel's ABI.

---
 Documentation/bpf/bpf_design_QA.rst | 6 ++++++
 1 file changed, 6 insertions(+)
Documentation/bpf/bpf_design_QA.rst +6 -0
index 437de2a7a5de7..2ed9128cfbec8 100644
@@ -214,6 +214,12 @@ A: NO. Tracepoints are tied to internal implementation details hence they are
 subject to change and can break with newer kernels. BPF programs need to change
 accordingly when this happens.
 
+Q: Are places where kprobes can attach part of the stable ABI?
+--------------------------------------------------------------
+A: NO. The places to which kprobes can attach are internal implementation
+details, which means that they are subject to change and can break with
+newer kernels. BPF programs need to change accordingly when this happens.
+
 Q: How much stack space a BPF program uses?
 -------------------------------------------
 A: Currently all program types are limited to 512 bytes of stack
Signature · 1 line
2.31.1.189.g2e36527f23