diff options
| author | Tej Singh <singhtejinder@google.com> | 2019-11-14 11:59:48 -0800 |
|---|---|---|
| committer | Tej Singh <singhtejinder@google.com> | 2020-02-19 19:02:06 -0800 |
| commit | 051001c41f60a6204ddf3d9d48a7b477606886e2 (patch) | |
| tree | 441c61c5f0c6184e4ef83062984b152fd075fe90 /tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp | |
| parent | 9dd718c5d91f459b1c07077c288d5b56c819c70f (diff) | |
Fix Race Condition
Currently, it is possible for two threads in statsd to concurrently
access/modify memory in ConditionTrackers since they do not have locks.
This happens when one thread is processing LogEvents (lock on
StatsLogProcessor mutex), while the other thread receives uidmap updates
and locks on the mutex in the MetricProducer. This Cl changes uidmap
updates to also go through the mutex in StatsLogProcessor.
This is a cherry pick from internal.
Test: bit statsd_test:*
Test: atest CtsStatsdHostTestCases
Test: local test that forced the race condition now passes
Bug: 144373785
Change-Id: I04ae2f7ed025f5ce8bc4fdeb7f10717e20d76282
Merged-In: I04ae2f7ed025f5ce8bc4fdeb7f10717e20d76282
Diffstat (limited to 'tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp')
0 files changed, 0 insertions, 0 deletions