Skip to content
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

Mv iter close fix #117

Merged
merged 5 commits into from
Jun 20, 2014
Merged

Mv iter close fix #117

merged 5 commits into from
Jun 20, 2014

Conversation

matthewvon
Copy link
Contributor

Correct race condition in asynchronous close logic that leads to segfaults. The bad code was merged to develop via the mv-tuning7 branch.

Detail discusssion is here: https://github.com/basho/leveldb/wiki/mv-iter-close-fix

@vinoski
Copy link
Contributor

vinoski commented Jun 20, 2014

+1

vinoski added a commit that referenced this pull request Jun 20, 2014
@vinoski vinoski merged commit e6bfbfe into develop Jun 20, 2014
@@ -954,7 +954,8 @@ async_close(
// verify that Erlang has not called DbObjectResourceCleanup
// already (that would be bad)
if (NULL!=db_ptr->m_Db
&& compare_and_swap(db_ptr->m_ErlangThisPtr, db_ptr.get(), (DbObject *)NULL))
// && compare_and_swap(db_ptr->m_ErlangThisPtr, db_ptr.get(), (DbObject *)NULL))
Copy link
Contributor

Choose a reason for hiding this comment

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

any reason to leave commented code in?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Awaiting next round of changes to clean up. With this bug, never completely sure if you are finished.

@seancribbs seancribbs deleted the mv-iter-close-fix branch April 1, 2015 22:45
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.

3 participants