diff options
| author | Mohammad Samiul Islam <samiul@google.com> | 2020-04-23 16:23:21 +0100 |
|---|---|---|
| committer | Songchun Fan <schfan@google.com> | 2022-01-11 22:54:46 +0000 |
| commit | 6151941007e9d85fc9279d46af20d8dc6b09744f (patch) | |
| tree | 451c031695139d1b84991d0c1304b1413c1722cc /rs/java/android/renderscript/ProgramFragmentFixedFunction.java | |
| parent | 5e154e8d5b8e5188791c53dc561be9afee5461d6 (diff) | |
Persist destroyed staged sessions until they are cleaned up
Currently, when we abandon a staged session we mark it as destroyed and
then immediately clean it up. Cleaning up a staged session immediately
causes racing condition with pre-reboot verification.
In order to avoid the racing condition, we want to delay cleanup of
staged session until it is safe to do so. This means, the system will
be carrying around destroyed staged sessions internally.
Since there is now a gap between when a session is destroyed and when it
is cleaned up, the user can reboot in this window. As such, we need to
persist the mDestroyed field of session so that we know session is
destroyed after reboot and act accordingly.
Also, once a session is destroyed, theoretically it doesn't exist.
Carrying it around internally is an implementation details which
shouldn't be exposed externally. As such, we filter out destroyed
sessions before surfacing them to users.
Bug: 145925842
Bug: 67862680
Test: atest PackageInstallerSessionTest
Test: atest StagedInstallTest
Change-Id: I4ede6b7a4b5d861e5c73f13884c7aa86cf7633a2
Merged-In: I4ede6b7a4b5d861e5c73f13884c7aa86cf7633a2
(cherry picked from commit 731bd965fb5e0f62dc703d05983baef8e0a0f4e7)
Diffstat (limited to 'rs/java/android/renderscript/ProgramFragmentFixedFunction.java')
0 files changed, 0 insertions, 0 deletions