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

Revive read-tickets WIP #930

Closed
wants to merge 1 commit into from
Closed

Revive read-tickets WIP #930

wants to merge 1 commit into from

Conversation

graydon
Copy link
Contributor

@graydon graydon commented Jul 5, 2023

Taking over from #132 which had bitrotted. Still WIP.

@graydon graydon mentioned this pull request Jul 5, 2023
2 tasks
@graydon graydon self-assigned this Jul 5, 2023
@graydon graydon added the Security Security fixes or features label Jul 5, 2023
@graydon graydon force-pushed the read-tickets-redux branch 2 times, most recently from f05e436 to e43de82 Compare July 6, 2023 08:10
@@ -18,11 +20,74 @@ use super::{
U64Object, Val, VecObject,
};

/// A ticket is a number that represents permission to read a set of host
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe I am missing something... but because objects have to be passed in as argument in order to be visible, this seems maybe over complicated? I think the only thing to keep track of is how deep in the stack something was shared.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No, it's unfortunately much more complicated than that. As a minimal example speaking to your question: if A calls B(x), then x should be readable by B, sure; but if B returns and A then calls C(y), x should not be readable by C, even though C is "at the same call depth" as B was.

@graydon
Copy link
Contributor Author

graydon commented Jul 14, 2023

closing in favor of #947

@graydon graydon closed this Jul 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Security Security fixes or features
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants