diff options
| author | 2022-03-17 17:54:25 -0700 | |
|---|---|---|
| committer | 2022-04-15 09:34:44 +0000 | |
| commit | 6e0d64b95ad932747cd1eff55d4d4d6d87460dc8 (patch) | |
| tree | b1474aabd72374ff885def48a10fbd182ffb4e64 /libs/androidfw/StringPool.cpp | |
| parent | d25240eb2573994efb511ff58dcda1a6e1e11aed (diff) | |
Guard mUidBlockedState with a separate lock.
Instead of using the main 'mUidRulesFirstLock', add a
granular lock for mUidBlockedState so that network state
requests (which only use mUidBlockedState) doesn't get
blocked on the highly contended 'mUidRulesFirstLock'.
The risk with this change is that it is possible the
underlying firewall rules are not consistent with the
network blocked state that is returned to the apps.
But technically, this is already case if there is an
immediate update to network rules after app queries
it's network access state.
Bug: 209338078
Test: atest tests/cts/hostside/src/com/android/cts/net/HostsideRestrictBackgroundNetworkTests.java
Change-Id: I6a913742647577256c9281dd8ebf4aa5422a49ee
Merged-In: I6a913742647577256c9281dd8ebf4aa5422a49ee
Diffstat (limited to 'libs/androidfw/StringPool.cpp')
0 files changed, 0 insertions, 0 deletions