Remove inactive container boot storage files and prevent it from
regenerated
The fix includes two part, both are guarded by the bugfix flag
bluetooth_flag_value_bug_fix
The changes is in two parts:
(1) make sure we always clear up last boot's boot storage files.
(2) for inactive containers, make sure the storage files object are not
created by aconfigd. so aconfigd will not create new boot copies for
these inactive containers.
When the boot copies for these inactive containers are out. Zygote will
not be able utilize these containers when creating a map from package
name to storage file set. Thus preventing these inactive container
storage files from being accidently used.
NOTE: this is a short term fix. A more involved long term fix will come
later that aims at reduce java flag read lib surface, and use native
side of infra for java flag reading as much as possible.
Bug: 391802823
Test: m and launch a virtual machine, add some random boot files and
reboot, observe that they are gone after reboot.
Change-Id: I6d0bbc5d62d51a535944664241279046521ba26e
5 files changed
