diff options
| author | 2022-10-14 19:05:04 +0000 | |
|---|---|---|
| committer | 2022-10-14 20:26:20 +0000 | |
| commit | 0954015735aff6123357f20b8310db7d81cfdd1b (patch) | |
| tree | cb67cdd515e01911e9eb8e306fdf0f9d54551ecf /tests/DynamicCodeLoggerIntegrationTests | |
| parent | d5d106aea962b5d2b9b52fcac64c722ad3504324 (diff) | |
Fix locksettings state removal on user removal
http://ag/19542373 (commit 78e245a21a11) made locksettings state removal
happen later during user removal than it did before. Unfortunately,
this made it stop working properly, since by the time it runs, the
/data/system_de/$userId/spblob/ directory has been locked by
StorageManager.destroyUserKey(). As a result, resources used by
synthetic password protectors, e.g. Weaver slots, stopped being freed.
Fix this by cleaning up the lock settings state *before* destroying the
user keys.
Bug: 232452368
Bug: 253631183
Test: 'pm create-user 10 && pm remove-user 10', then checked log to
verify that the Weaver slot was removed.
Change-Id: Ib3e7586bfde37632b77c7655bc91692ee6daad86
Diffstat (limited to 'tests/DynamicCodeLoggerIntegrationTests')
0 files changed, 0 insertions, 0 deletions