Drive-by fix for wtfIfInLock + two violations
wtfIfInLock() method was checking 'this' lock while the code is actually using mLockDoNoUseDirectly returned by getLockObject(), thus violation werent reported. This CL changes this and fixes violations when calling hasIncompatibleAccountsOrNonAdbNoLock. Also move it to other lock-related methods. Bug: 162815601 Test: atest com.android.cts.devicepolicy.DeviceOwnerTest#testDeviceOwnerSetup Test: atest com.android.cts.devicepolicy.ProfileOwnerTest#testManagement Test: manual: add account, attempt setting a DO Change-Id: Id64930552f5a9b25464ba942b0b1ddbe9378928e
Loading
Please register or sign in to comment