ts::shared_mutex - Fix lock counting for debug #9040
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Lock count variable was left uninitialized, causing assertions to fail. This change initializes the debug data so they work properly. Also add a similar check to the locking side.
ywkaras
reviewed
Aug 16, 2022
| X(std::atomic<bool> _exclusive;) | ||
| X(std::atomic<int> _shared;) | ||
| X(std::atomic<bool> _exclusive{false};) | ||
| X(std::atomic<int> _shared{0};) |
Contributor
Author
There was a problem hiding this comment.
According to this: https://en.cppreference.com/w/cpp/atomic/atomic/atomic
The default constructor is trivial: no initialization takes place other than zero initialization of static and thread-local objects. std::atomic_init may be used to complete initialization.
I also ran into an uninitialized value during local testing, which drove this change.
Contributor
There was a problem hiding this comment.
Oops, sorry, I thought the std::atomic constructor always zero initialized, even for stack instances.
ywkaras
approved these changes
Aug 16, 2022
Contributor
|
Cherry-picked to v9.2.x |
zwoop
pushed a commit
that referenced
this pull request
Aug 23, 2022
Lock count variable was left uninitialized, causing assertions to fail. This change initializes the debug data so they work properly. Also add a similar check to the locking side. (cherry picked from commit 2e31ef8)
cmcfarlen
pushed a commit
to cmcfarlen/trafficserver
that referenced
this pull request
Aug 23, 2022
Lock count variable was left uninitialized, causing assertions to fail. This change initializes the debug data so they work properly. Also add a similar check to the locking side.
masaori335
pushed a commit
to masaori335/trafficserver
that referenced
this pull request
Feb 21, 2023
* asf/9.2.x: Updated ChangeLog utilize proxy.config.hostdb.host_file.interval config variable (apache#9039) Remove plugin parent_select unused symbols (apache#9023) Require use of 'override' keyword when valid. (apache#8737) Fix compile error on macOS (apache#9047) Validate that content length header matches object size on cache read (apache#8976) Fix reload memory leak (apache#9041) Update prepare_proxy_verifier.sh to work in non-git directories (apache#9048) Change linux/fs include to build with glibc 2.36 (apache#9027) ts::shared_mutex - Fix lock counting for debug (apache#9040)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Lock count variable was left uninitialized, causing assertions to fail.
This change initializes the debug data so they work properly. Also add
a similar check to the locking side.