v8/tools/sanitizers/tsan_suppressions.txt

# Suppressions for TSan v2
# https://code.google.com/p/thread-sanitizer/wiki/Suppressions

# Incorrectly detected lock cycles in test-lockers
# https://code.google.com/p/thread-sanitizer/issues/detail?id=81
deadlock:LockAndUnlockDifferentIsolatesThread::Run

# A global safepoint might lock client isolate mutexes in any order, which
# would be reported as potential deadlocks.
deadlock:GlobalSafepoint::EnterGlobalSafepointScope
Introduce a tsan suppressions file Also suppress a deliberate lock cycle in test-lockers BUG=none R=glider@chromium.org, machenbach@chromium.org LOG=n Review URL: https://codereview.chromium.org/642023002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24484 ce2b1a6d-e550-0410-aec6-3dcde31c8c00 2014-10-09 09:32:04 +00:00			`# Suppressions for TSan v2`
			`# https://code.google.com/p/thread-sanitizer/wiki/Suppressions`

Add link to tsan bug to suppression TBR=machenbach@chromium.org LOG=n BUG=none Review URL: https://codereview.chromium.org/646493002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24487 ce2b1a6d-e550-0410-aec6-3dcde31c8c00 2014-10-09 09:51:21 +00:00			`# Incorrectly detected lock cycles in test-lockers`
			`# https://code.google.com/p/thread-sanitizer/issues/detail?id=81`
Introduce a tsan suppressions file Also suppress a deliberate lock cycle in test-lockers BUG=none R=glider@chromium.org, machenbach@chromium.org LOG=n Review URL: https://codereview.chromium.org/642023002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24484 ce2b1a6d-e550-0410-aec6-3dcde31c8c00 2014-10-09 09:32:04 +00:00			`deadlock:LockAndUnlockDifferentIsolatesThread::Run`
Reland "[heap] Optimize time to reach global safepoint" This is a reland of 86038ecfdc8315e394880a9decfa1bbda7d11748 Compared to the previous CL this one is adding a TSAN suppression for GlobalSafepoint::EnterSafepointScope. local_heaps_mutex_ of client isolates may be locked in any order. This would be detected by TSAN as a potential race. Add some additional DCHECKs to compensate for that missing test coverage. As a cleanup this CL also removes the unused methods ContainsLocalHeap() and ContainsAnyLocalHeap() from LocalHeap. Original change's description: > [heap] Optimize time to reach global safepoint > > Initial support for global safepoints kept it simple by entering a > safepoint for each of them one after another. This means > time-to-global-safepoint is the sum of all time-to-safepoint operations. > We can improve this slightly by splitting up the safepoint iteration > into two operations: > > 1) Initiate safepoint lock (locks local_heaps_mutex_, arms the barrier > and sets SafepointRequested flag for all client threads) > 2) Block until all runnning client threads reach a safepoint > > We now perform operation 1) for all clients first and only then start > with operation 2). > > Bug: v8:11708 > Change-Id: Iaafd3c6d70bcf7026f722633e9250b04148b3da6 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3310910 > Reviewed-by: Michael Lippautz <mlippautz@chromium.org> > Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> > Cr-Commit-Position: refs/heads/main@{#78308} Bug: v8:11708, v8:12492 Change-Id: I7087ba23c08f2d4edb9b632eef3c218fc76342e7 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3328786 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Cr-Commit-Position: refs/heads/main@{#78583} 2021-12-10 14:49:54 +00:00
			`# A global safepoint might lock client isolate mutexes in any order, which`
			`# would be reported as potential deadlocks.`
			`deadlock:GlobalSafepoint::EnterGlobalSafepointScope`