bpf: enforce returning 0 for fentry/fexit programs
Status from this message: Applied to bpf tree with that typo fixed. Thanks
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest2 patches 4 repliesApplied
- v12 patches 2 repliesSuperseded
Changes in v2 from the cover letter
- explicitly specify expected return value ranges for all attach types of the tracing programs. Any unspecified attach type will return an error. This will force any future tracing attach_type to be explicit about its return value range (Andrii).
Patches in v2 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | bpf: enforce returning 0 for fentry/fexit progskernel/ | +18 | 3 replies | |
| 2/2 | selftests/bpf: enforce returning 0 for fentry/fexit programstools/ | +2 | 1 reply |
Reviews trailers per patch
All 2 patches have a Reviewed-by or Acked-by.
| Patch | Andrii Nakryiko |
|---|---|
| 1/2 | A-b |
| 2/2 | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH bpf v2 0/2] bpf: enforce returning 0 for fentry/fexit programs
Currently, tracing fentry/fexit program return value can be anything, and these return values are actually ignored by trampoline codes. Let us force return value to be 0 to avoid confusion and allow possible future extension. Patch #1 is the kernel change and Patch #2 fixed the selftest.
Changelog:
v1 -> v2:
- explicitly specify expected return value ranges for all attach types of the tracing programs. Any unspecified attach type will return an error. This will force any future tracing attach_type to be explicit about its return value range (Andrii).
Yonghong Song (2):
bpf: enforce returning 0 for fentry/fexit progs selftests/bpf: enforce returning 0 for fentry/fexit programs
kernel/bpf/verifier.c | 18 ++++++++++++++++++ .../selftests/bpf/progs/test_overhead.c | 4 ++-- 2 files changed, 20 insertions(+), 2 deletions(-)
Signature · 1 line
2.24.1