-
Notifications
You must be signed in to change notification settings - Fork 68
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
3 step protocol for cap active needs to be fixed #363
Comments
To add more detail: The three-step protocol for capability activation is meant to address races between two capability activations in the same slot. Currently, the code in the repo simply doesn't do this. The abstractions of the code abide by the 3 step protocol, but the implementation of that abstraction does not. BUG. The three steps are:
Note that once a slot is active, it is immutable with very few exceptions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 step protocol for cap active needs to be fixed. There is a bug in this function.
The text was updated successfully, but these errors were encountered: