Merge "UserManagerService: fix comment for mRemovingUserIds" am: 030c47cbfb am: 2cf8cd28fa

Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/2115419

Change-Id: Ifd7cf5ad44bd2df4fcd1c0075ce4f9baa30ddcd3
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
This commit is contained in:
Eric Biggers
2022-06-10 00:27:10 +00:00
committed by Automerger Merge Worker

View File

@@ -443,9 +443,12 @@ public class UserManagerService extends IUserManager.Stub {
private final Bundle mGuestRestrictions = new Bundle();
/**
* Set of user IDs being actively removed. Removed IDs linger in this set
* for several seconds to work around a VFS caching issue.
* Use {@link #addRemovingUserIdLocked(int)} to add elements to this array
* Set of user IDs that are being removed or were removed during the current boot. User IDs in
* this set aren't reused until the device is rebooted, unless MAX_USER_ID is reached. Some
* services don't fully clear out in-memory user state upon user removal; this behavior is
* intended to mitigate such issues by limiting user ID reuse. This array applies to any type
* of user (including pre-created users) when they are removed. Use {@link
* #addRemovingUserIdLocked(int)} to add elements to this array.
*/
@GuardedBy("mUsersLock")
private final SparseBooleanArray mRemovingUserIds = new SparseBooleanArray();