android_packages_modules_Co.../bpf/loader
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Maciej Żenczykowski db324dfbca NetBpfLoad: eliminate 'bpfCmdFixupIsNeeded'
It turns out this doesn't work anyway:

Both our Java and C++ higher level map opening logic on 4.14+
kernels will check key/value sizes match, which will fail due to
the kernel uapi mismatch.

(Note: that the fixup was only ever applied/enabled inside of
the NetBpfLoad process itself, not in any later .so/Java/JNI)

This removes the fixup and simply chooses to not even attempt to
load bpf.  This will result in the mainline bpf provided
maps and programs simply not existing.  This would/will cause
a failure of 'bpf_existence_test' - but who cares, so long
as things keep on booting.

We need to transition to libbpf, and clearly making this work
isn't worth the considerable effort it would be, since S ebpf
functionality (ie. tethering offload) hasn't worked on the
affected devices in years.

Test: TreeHugger
Flag: EXEMPT mainline
Signed-off-by: Maciej Żenczykowski <maze@google.com>
Change-Id: Ic93a5a9d5b3ba8078500e20dfdf00ef68256874c
2025-09-11 13:01:01 -07:00
..
initrc-doc NetBpfLoad: doc updates... 2024-10-02 22:48:44 +00:00
Android.bp NetBpfLoad: use libbpf based on mainline beta flag 2025-08-22 22:46:24 +09:00
netbpfload.31rc bpf: switch to mainline netbpfload on Android S/SV2 2025-03-05 14:27:59 -08:00
netbpfload.33rc Revert "bpf: change NetBpfLoad rc file from 33 (T/U) to 31 (S/Sv2/T/U)" 2025-03-04 21:54:09 -08:00
netbpfload.35rc netbpfload.35rc: grant capability SYSLOG if available 2025-08-14 20:10:43 -07:00
NetBpfLoad.cpp NetBpfLoad: eliminate 'bpfCmdFixupIsNeeded' 2025-09-11 13:01:01 -07:00
netbpfload.rc netbpfload.rc: update for 25Q4 2025-06-11 08:09:57 -07:00