98ad32a967
Currently if a process sets the sys.powerctl property, init adds this property change into the event queue, just like any other property. The actual logic to shutdown the device is not executed until init gets to the action associated with the property change. This is bad for multiple reasons, but explicitly causes deadlock in the follow scenario: A service is started with `exec` or `exec_start` The same service sets sys.powerctl indicating to the system to shutdown The same service then waits infinitely In this case, init doesn't process any further commands until the exec service completes, including the command to reboot the device. This change causes init to immediately handle sys.powerctl and reboot the device regardless of the state of the event queue, wait for exec, or wait for property conditions. Bug: 37209359 Bug: 37415192 Test: Init reboots normally Test: Update verifier can reboot the system Change-Id: Iff2295aed970840f47e56c4bacc93001b791fa35 |
||
|---|---|---|
| .. | ||
| etc | ||
| Android.mk | ||
| asan.options | ||
| asan.options.off.template | ||
| init-debug.rc | ||
| init.environ.rc.in | ||
| init.rc | ||
| init.usb.configfs.rc | ||
| init.usb.rc | ||
| init.zygote32.rc | ||
| init.zygote32_64.rc | ||
| init.zygote64.rc | ||
| init.zygote64_32.rc | ||
| ueventd.rc | ||