-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Race Conditions in qutil
#238
Comments
Poking at some of the memory fences for syncvars seems like a partial fix. Some additional atomics in the nemesis scheduler may be necessary to get the sequencing right, but at this point I'm still not sure. The weird thing though is that some of the thread sanitizer tracebacks here seem to be getting garbled and it's not at all clear why/how that's happening. It may be that a better-debugged #249 is needed to fix these warnings. |
I'm seeing a handful of thread sanitizer errors about race conditions in the
qutil
code.One example: apparently the macro invoked at
qthreads/src/qutil.c
Line 152 in a2d1dba
qthreads/src/qutil.c
Line 156 in a2d1dba
qthreads/src/qutil.c
Line 160 in a2d1dba
Another example:
non-atomic read:
qthreads/src/qutil.c
Line 897 in a2d1dba
atomic write to the same variable:
qthreads/src/qutil.c
Line 903 in a2d1dba
Similar:
qthreads/src/qutil.c
Line 909 in a2d1dba
qthreads/src/qutil.c
Line 915 in a2d1dba
Another more unusual one:
The macro invoked at
qthreads/src/qutil.c
Line 170 in a2d1dba
qthread_syncvar_fill
atqthreads/src/syncvar.c
Line 609 in a2d1dba
The text was updated successfully, but these errors were encountered: