init: Allow restricted use of binder.
Allow init to use binder, but in a restricted way: - No binder threadpool - Other processes can't initiate calls to init - No death recipients This change adds libbinder/libutils and calls into ProcessState, which also calls into the kernel driver and sets up state there. No other binder calls are made, so that we can let this soak for a while to see if there any bad side effects of just loading these libraries and initializing the kernel driver. This introduces about 120kB of additional memory usage (PSS), mostly due to pulling in libbinder and libutils and the private state they have. We also don't include these libraries in the recovery version of init, because space on the recovery partition is limited. Bug: 112684055 Test: device still boots, /d/binder/proc/1 shows init state Change-Id: I972b1eebdb16337f52e20d1f614e3a0dce0f06d2
Loading
Please register or sign in to comment