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

Race Conditions #1

Open
eriq-augustine opened this issue Aug 16, 2017 · 0 comments
Open

Race Conditions #1

eriq-augustine opened this issue Aug 16, 2017 · 0 comments

Comments

@eriq-augustine
Copy link
Owner

There are race conditions all over the place.
In pretty much every operation.

The real question is how we decide to handle them.
Should we:

  • lock the driver on every command
  • lock on the file level
  • force the external caller to lock

At the driver level, the only critical concern is that that fat is not corrupted.
We will even tolerate things like incorrect access dates or counts as long as the filename and iv remains intact.

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

No branches or pull requests

1 participant