You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
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.
The text was updated successfully, but these errors were encountered: