Fix usage of the wrong lock in PackageManager (mLock instead of mSettings)

Bug: 162757028
Bug: 166537195
Test: compile & verify basic functions working
Change-Id: Ie822d8f2267dcb8ce382e91ab5de365a4e0ce19f
Merged-In: Ie822d8f2267dcb8ce382e91ab5de365a4e0ce19f
(cherry picked from commit 1690689bc44d82d57e9ea12d44ef32d18dcb1326)
diff --git a/services/core/java/com/android/server/pm/PackageManagerService.java b/services/core/java/com/android/server/pm/PackageManagerService.java
index eefad1c..0cec95d 100644
--- a/services/core/java/com/android/server/pm/PackageManagerService.java
+++ b/services/core/java/com/android/server/pm/PackageManagerService.java
@@ -14501,7 +14501,7 @@
         final PackageSetting ps;
         int appId = -1;
         long ceDataInode = -1;
-        synchronized (mSettings) {
+        synchronized (mLock) {
             ps = mSettings.getPackageLPr(packageName);
             if (ps != null) {
                 appId = ps.appId;