bpf: don't spam the log with initMaps successfully
We already log on init start, and we log all failures, we don't need an extra log in the middle of init. I NetdUpdatable: libnetd_updatable_init: Initializing I NetdUpdatable: initMaps successfully E NetdUpdatable: libnetd_updatable_init: Failed: (1) [Operation not permitted] : Failed to change RLIMIT_MEMLOCK to 2 GiB while success looks like: I netd : netd 1.0 starting I netd : Pid file removed I netd : SIGPIPE is blocked I netd : setCloseOnExec(dnsproxyd) I netd : setCloseOnExec(fwmarkd) I NetdUpdatable: libnetd_updatable_init: Initializing I NetdUpdatable: BPF programs are loaded I NetdUpdatable: initMaps successfully I netd : libnetd_updatable_init success I netd : NetlinkManager instanced Test: TreeHugger Signed-off-by: Maciej Żenczykowski <maze@google.com> Change-Id: I8bca9b59363c1f31ecf3de80b9d280a28cce4a14
This commit is contained in:
parent
e771525f4f
commit
6fc914642c
1 changed files with 0 additions and 1 deletions
|
|
@ -318,7 +318,6 @@ Status BpfHandler::initMaps() {
|
|||
RETURN_IF_NOT_OK(mUidPermissionMap.init(UID_PERMISSION_MAP_PATH));
|
||||
// initialized last so mCookieTagMap.isValid() implies everything else is valid too
|
||||
RETURN_IF_NOT_OK(mCookieTagMap.init(COOKIE_TAG_MAP_PATH));
|
||||
ALOGI("%s successfully", __func__);
|
||||
|
||||
return netdutils::status::ok;
|
||||
}
|
||||
|
|
|
|||
Loading…
Reference in a new issue