| commit | f9a4bb18ffa1605cced3ee4b161675a0c88941be | [log] [tgz] |
|---|---|---|
| author | Tej Singh <singhtejinder@google.com> | Thu Sep 10 23:20:58 2020 -0700 |
| committer | Tej Singh <singhtejinder@google.com> | Fri Sep 11 06:27:36 2020 +0000 |
| tree | f4f46eda5c38439f4b3b99a1ce1241945e233751 | |
| parent | 8423c02906161de6b745c92a6a1562345dfb5f5a [diff] |
Fix thread safety issue on clearing cache Historically, we havent held a lock on ForceClearCache and ClearCacheIfNecessary. This is not thread safe because kAllPullAtomInfo must be accessed in a lock, especially now that pullers can be registered/unregistered. Test: atest statsd_test, wrote a repro cl. Bug: 168156854 Change-Id: I47d53a6d9d274bca4c78dbfd87e0097091b7b8cb