-
Notifications
You must be signed in to change notification settings - Fork 10
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
Validate operations on FileHandles #1113
Conversation
This commit allows State to track whether a file handle is valid for read etc operations. Our GC mechanism keeps track of the open-handles but assumes the correctness of callers, meaning if multiple calls to `release` are made at the filesystem level a node may be GC'ed before its time. The State now keeps a record of which FileHandles exist and whether they remain valid, meaning the GC mechanism cannot be misled. REF SMPTNG-532 Signed-off-by: Brian L. Troutwine <[email protected]>
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Signed-off-by: Brian L. Troutwine <[email protected]>
Signed-off-by: Brian L. Troutwine <[email protected]>
!valid_handles.is_empty(), | ||
"Unlinked, read-only file with open handles should have valid file handles" | ||
); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: indentation is off here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So it is and cargo-fmt didn't catch it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Macros :( There was a google summer of code project that I think will improve this in the next few releases.
Signed-off-by: Brian L. Troutwine <[email protected]>
What does this PR do?
This commit allows State to track whether a file handle is valid for read etc
operations. Our GC mechanism keeps track of the open-handles but assumes the
correctness of callers, meaning if multiple calls to
release
are made at thefilesystem level a node may be GC'ed before its time.
The State now keeps a record of which FileHandles exist and whether they remain
valid, meaning the GC mechanism cannot be misled.
Motivation
SMPTNG-531