summaryrefslogtreecommitdiff
path: root/tools/aapt2/java/JavaClassGenerator.cpp
diff options
context:
space:
mode:
authorEric Biggers <ebiggers@google.com>2021-04-06 12:02:49 -0700
committerEric Biggers <ebiggers@google.com>2021-04-08 12:29:19 -0700
commit270db90c37abdded2c251c93b671869c2632dd3b (patch)
tree29e4feca46c873766c74ab40670f005a6f916d6f /tools/aapt2/java/JavaClassGenerator.cpp
parent006b746b5c268620207a5a4eaf2c33792d21ee47 (diff)
Get list of unlocked users from vold
When StorageManagerService is started, initialize mLocalUnlockedUsers to the list of users that vold knows is unlocked rather than an empty list. This fixes StorageManagerService.isUserKeyUnlocked() to return true instead of false for already-unlocked users after a userspace reboot. So far this bug hadn't been causing real problems, since UserController will always try to unlock users without providing a secret, and that happened to succeed with a vold warning for users that vold already knows are unlocked -- even if a secret would normally be required. However, in order to eliminate misleading error messages from the log, system_server needs to stop asking vold to unlock users that require a secret without providing one. To keep that from breaking userspace reboot, we need to fix mLocalUnlockedUsers to properly reflect the initial state and not have to be fixed up "by accident" later. Bug: 146206679 Test: see I482ed8017f7bbc8f7d4fd5a2c0f58629317ce4ed Change-Id: Ife12ba9fbb2e65822b8d54de8f7a050b6ebe10a9
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator.cpp')
0 files changed, 0 insertions, 0 deletions