-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
MFS: Race when reading node and taking read/write lock #4514
Comments
Stebalien
added a commit
that referenced
this issue
Dec 21, 2017
Otherwise, it could be exchanged out from under us! fixes #4514 License: MIT Signed-off-by: Steven Allen <[email protected]>
Closed
Stebalien
added a commit
that referenced
this issue
Dec 21, 2017
Otherwise, it could be exchanged out from under us! fixes #4514 License: MIT Signed-off-by: Steven Allen <[email protected]>
Closed
Stebalien
added a commit
that referenced
this issue
Dec 21, 2017
Otherwise, it could be exchanged out from under us! fixes #4514 License: MIT Signed-off-by: Steven Allen <[email protected]>
Closed
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We currently read the node (under the node lock), then take the read/write lock. However, a racing thread could also read the node, then take the write lock before us, update the node, and write it back. We'll then take the read (or write) lock and see the old node, not the new one.
The text was updated successfully, but these errors were encountered: