09833df2d9
The two AssociatedGroupController implementations we have both own a lock which is acquired during message dispatch, among other operations. In the EDK layer a Watcher lock is also acquired further up the stack. Because sending a message may indirectly require notifying the same Watcher lock, it must never be true that the AssociatedGroupController's lock is held while its pipe is written to. This fixes the lock-order inversion resulting from the fact that pipe control messages were being sent under lock, and removes the associated TSAN suppression. BUG=663557 TBR=glider@chromium.org R=yzshen@chromium.org Review-Url: https://codereview.chromium.org/2494483003 Cr-Original-Commit-Position: refs/heads/master@{#431331} Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src Cr-Mirrored-Commit: 58909542197b704efe10526c169e4b502f799b57 |
||
---|---|---|
.. | ||
BUILD.gn | ||
OWNERS | ||
asan_suppressions.cc | ||
lsan_suppressions.cc | ||
sanitizer_options.cc | ||
tsan_suppressions.cc |