Fix instance of using mPackages as the lock

It looks like the day that the switch to mLock went in, another change
merged in that added code that included synchronization on mPackages.
This gets us back to only using mLock.

Test: Builds
Bug: N/A
Change-Id: I6c9332a135efd4f0189ed6f27f43ba51f025cf8f

1 files changed, 1 insertions, 1 deletions

diff --git a/services/core/java/com/android/server/pm/PackageManagerService.java b/services/core/java/com/android/server/pm/PackageManagerService.java
index d07e2d232ea6..0fbe992da47b 100644
--- a/services/core/java/com/android/server/pm/PackageManagerService.java
+++ b/services/core/java/com/android/server/pm/PackageManagerService.java
@@ -20270,7 +20270,7 @@ public class PackageManagerService extends IPackageManager.Stub
                     mInjector.getPermissionPolicyInternal();
             permissionPolicyInternal.setOnInitializedCallback(userId -> {
                 // The SDK updated case is already handled when we run during the ctor.
-                synchronized (mPackages) {
+                synchronized (mLock) {
                     mPermissionManager.updateAllPermissions(
                             StorageManager.UUID_PRIVATE_INTERNAL, false);
                 }