Skip to content

array: More locking fixes#400

Merged
chrissie-c merged 2 commits intoClusterLabs:masterfrom
chrissie-c:more-locking-fixes
Jun 8, 2020
Merged

array: More locking fixes#400
chrissie-c merged 2 commits intoClusterLabs:masterfrom
chrissie-c:more-locking-fixes

Conversation

@chrissie-c
Copy link
Copy Markdown
Contributor

helgrind threw out a couple more locking errors in the logging/array
code.

helgrind threw out a couple more locking errors in the logging/array
code.
@jfriesse
Copy link
Copy Markdown
Member

jfriesse commented Jun 5, 2020

Looks good but I have one question. Is it safe to access a->max_elements (qb_array_index function) without locking?

@chrissie-c
Copy link
Copy Markdown
Contributor Author

Hmm good question. Helgrind didn't complain about it but that's not a guarantee

Copy link
Copy Markdown
Member

@jfriesse jfriesse left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, helgrind is usually right so ACK because patch improves locking for sure. We may consider more enhancements if it shows as needed later.

Copy link
Copy Markdown
Member

@jfriesse jfriesse left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems good so ACK.

@chrissie-c chrissie-c merged commit b2acdea into ClusterLabs:master Jun 8, 2020
@chrissie-c
Copy link
Copy Markdown
Contributor Author

thanks for the review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants