diff options
| author | Tom Cherry <tomcherry@google.com> | 2019-05-21 13:53:05 -0700 |
|---|---|---|
| committer | Keun young Park <keunyoung@google.com> | 2019-05-30 12:10:51 -0700 |
| commit | b80149d8bc5ec67fc1f22a1c248a4ff7d081f620 (patch) | |
| tree | 2ca1dbac23441889879a8a0f6d99a5d32682b298 /trusty/coverage/coverage.cpp | |
| parent | 1fcd51255a8eb1bf2e114ab9fcda73ecc0ac05b4 (diff) | |
init: make fatal reboot target configurable
Currently, if init encounters a fatal issues it reboots to fastboot
but this may be not desirable in all cases, especially the case of
critical services crashing. Therefore this change adds the ability
for vendors to customize the reboot target via the
androidboot.init_fatal_reboot_target= kernel command line.
This applies to all LOG(FATAL) messages as well as fatal signals in
userdebug/eng builds, except for signals before logging is enabled in
first stage init.
Bug: 121006328
Test: device reboots to configurable target with LOG(FATAL)
Test: device reboots to configurable target after a segfault in the
various stages of init
Test: device reboots to fastboot without a configured target
Change-Id: I16ea9e32e2fee08dece3d33b697d7a08191d607b
Merged-In: I16ea9e32e2fee08dece3d33b697d7a08191d607b
(cherry picked from commit 75e13baf32ae1a54a9e43b7d7d6bdcc6f8d545d7)
Diffstat (limited to 'trusty/coverage/coverage.cpp')
0 files changed, 0 insertions, 0 deletions