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
tsan: make detecting the need for locking when using tsan easier #17479
Conversation
The files that reference TSAN_QUALIFIER are:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, whether or not you want to fix the white space issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah sorry, overlooked the CI issue, which is relevant
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice.
the test case is master only stuff. |
Doing the tsan operations under lock would be difficult to arrange here (locks require memory allocation).
Most of the DRGB code is run under lock from the EVP layer. This is relied on to make the majority of TSAN operations safe. However, it is still necessary to enable locking for all DRBGs created.
Not all platforms support tsan operations, those that don't need to have an alternative locking path. Fixes openssl#17447
Reviewed-by: Bernd Edlinger <bernd.edlinger@hotmail.de> (Merged from #17479)
Reviewed-by: Bernd Edlinger <bernd.edlinger@hotmail.de> (Merged from #17479)
Reviewed-by: Bernd Edlinger <bernd.edlinger@hotmail.de> (Merged from #17479)
Reviewed-by: Bernd Edlinger <bernd.edlinger@hotmail.de> (Merged from #17479)
Doing the tsan operations under lock would be difficult to arrange here (locks require memory allocation). Reviewed-by: Bernd Edlinger <bernd.edlinger@hotmail.de> (Merged from #17479)
Reviewed-by: Bernd Edlinger <bernd.edlinger@hotmail.de> (Merged from #17479)
Most of the DRGB code is run under lock from the EVP layer. This is relied on to make the majority of TSAN operations safe. However, it is still necessary to enable locking for all DRBGs created. Reviewed-by: Bernd Edlinger <bernd.edlinger@hotmail.de> (Merged from #17479)
Merged to master. Manually cherry picked to 3.0 (needed to omit one test and the object change). |
Reviewed-by: Bernd Edlinger <bernd.edlinger@hotmail.de> (Merged from #17479)
Reviewed-by: Bernd Edlinger <bernd.edlinger@hotmail.de> (Merged from #17479)
Reviewed-by: Bernd Edlinger <bernd.edlinger@hotmail.de> (Merged from #17479)
Doing the tsan operations under lock would be difficult to arrange here (locks require memory allocation). Reviewed-by: Bernd Edlinger <bernd.edlinger@hotmail.de> (Merged from #17479)
Reviewed-by: Bernd Edlinger <bernd.edlinger@hotmail.de> (Merged from #17479)
Most of the DRGB code is run under lock from the EVP layer. This is relied on to make the majority of TSAN operations safe. However, it is still necessary to enable locking for all DRBGs created. Reviewed-by: Bernd Edlinger <bernd.edlinger@hotmail.de> (Merged from #17479)
TSAN has a number of problems currently.
Eventually this might fix #17447