Normally, the tid_count is initialized only once at the beginning of the
application. The only exception is the pattern in the unit test where
isc_loopmgr is repeatedly created and torn down and each creation of
isc_loopmgr_t calls isc__tid_initcount() with the previous value.
ThreadSanitizer sees that as write operation on unprotected memory are
reports this as data race even though the value has not really changed.
This has been fixed by skipping the tid_count value update on repeated
calls.
(cherry picked from commit
a570e37c067fc83e5d78698a118e8c8e45085498)
* information regarding copyright ownership.
*/
-#include <stdlib.h>
#include <sys/types.h>
#include <unistd.h>
void
isc__tid_initcount(uint32_t count) {
REQUIRE(tid_count == 0 || tid_count == count);
- tid_count = count;
+ if (tid_count == 0) {
+ tid_count = count;
+ }
}
/**