This PR adds to the ThreadDNSAddressSeed
and ThreadOpenAddedConnections
threads their own CThreadInterrupt
objects, and fixes ThreadSanitizer’s “double lock of a mutex” warnings.
Fix #19024
459@@ -460,6 +460,8 @@ class CConnman
460 Mutex mutexMsgProc;
461 std::atomic<bool> flagInterruptMsgProc{false};
462
463+ CThreadInterrupt g_interrupt_dnsseed_thread;
464+ CThreadInterrupt g_interrupt_addcon_thread;
0 CThreadInterrupt m_interrupt_addcon_thread;
Looks like a member to me, no?
Updated 7bb5707a533090e2b1cdc7e27b860b37b25651e1 -> a46122ca6503c780b303d2c8194625faeb8d0f65 (pr19029.01 -> pr19029.02, diff):
Looks like a member to me, no?
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
Reviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.
I’m not sure these warnings aren’t false positive due to the Fedora clang’s bug. See: #19024 (comment)
So closing for now.
An alternative would be to make the mutex recursive for now
This won’t compile, unfortunately.
Labels
P2P