joy/android_packages_modules_Connectivity
Watch
1
Fork
You've already forked android_packages_modules_Connectivity
 0
Code Issues Pull requests Projects Releases Wiki Activity

NetBpfLoad: 25Q2+ enforce 1GiB+ memlock

Browse source 
On at least some kernel versions sufficient memlock
is needed for some [types? larger? preallocated?]
bpf map creation requests to succeed.

(the kernel's bpf subsys ignores CAP_IPC_LOCK)

Test: TreeHugger
Signed-off-by: Maciej Żenczykowski <maze@google.com>
Change-Id: Ia6975e854e6398ee9c56ce836b278b570e17a0f9
This commit is contained in:
Maciej Żenczykowski 2025-03-20 11:50:17 -07:00
commit ba7a418cab
1 changed files with 10 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

10
bpf/netd/BpfHandler.cpp
View file

@ -268,6 +268,16 @@ Status BpfHandler::init(const char* cg2_path) {
RETURN_IF_NOT_OK(initMaps());
if (isAtLeast25Q2) {
struct rlimit limit = {
.rlim_cur = 1u << 30, // 1 GiB
.rlim_max = 1u << 30, // 1 GiB
};
// 25Q2 netd.rc includes "rlimit memlock 1073741824 1073741824"
// so this should be a no-op, and thus just succeed.
// make sure it isn't lowered in platform netd.rc...
if (setrlimit(RLIMIT_MEMLOCK, &limit))
return statusFromErrno(errno, "Failed to set 1GiB RLIMIT_MEMLOCK");
// Make sure netd can create & write maps. sepolicy is V+, but enough to enforce on 25Q2+
int key = 1;
int value = 123;