Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 42a0fed7 authored by Josh Gao's avatar Josh Gao
Browse files

init: don't start tombstoned until /data is mounted. 

When vold mounts the encrypted /data partition, it first checks for and
kills processes that have open fds to the tmpfs placeholder at /data.
This resulted in a 20 second boot-time regression (vold's timeout period)
when tombstoned was started before vold.

Bug: http://b/34461270
Test: boot is faster, no messages from vold in console spew
Test: tombstoned still started by init
Change-Id: Ib5e9ddb05f40c9da852f00e103861c6ff2d94888
parent 1e7cdf3c

debuggerd/tombstoned/tombstoned.rc

+0 −2
Original line number Diff line number Diff line 
service tombstoned /system/bin/tombstoned

    class core



    user tombstoned

    group system

rootdir/init.rc

+3 −4
Original line number Diff line number Diff line
@@ -356,14 +356,13 @@ on post-fs-data 
    # We restorecon /data in case the userdata partition has been reset.

    restorecon /data



    # start debuggerd to make debugging early-boot crashes easier.

    start debuggerd

    start debuggerd64



    # Make sure we have the device encryption key.

    start vold

    installkey /data



    # start tombstoned to record early-boot crashes.

    start tombstoned



    # Start bootcharting as soon as possible after the data partition is

    # mounted to collect more data.

    mkdir /data/bootchart 0755 shell shell