| commit | db097214b109be7ca1b3ae470d4a8354c98a5b62 | [log] [tgz] |
|---|---|---|
| author | Tej Singh <singhtejinder@google.com> | Thu Sep 10 23:20:58 2020 -0700 |
| committer | Tej Singh <singhtejinder@google.com> | Thu Jan 21 08:31:02 2021 +0000 |
| tree | f2d3aa706db9fd8b5b6dd883d373758a10184883 | |
| parent | 80a05232a04a5ef8df9f5e5fb0afd7471ea7eb38 [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 Bug: 173552790 Change-Id: I47d53a6d9d274bca4c78dbfd87e0097091b7b8cb Merged-In: I47d53a6d9d274bca4c78dbfd87e0097091b7b8cb Merged-In: I8bee7a0a6acecc1274d5acc0adb44c5dde8862e4 (cherry picked from commit f9a4bb18ffa1605cced3ee4b161675a0c88941be)