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

Fix unstable WRITE when first write fails to open file #49

Merged
merged 1 commit into from
Aug 30, 2017

Conversation

Toilal
Copy link
Contributor

@Toilal Toilal commented Aug 30, 2017

If something goes wrong on unstable WRITE when opening the file (Access Denied because it's flagged read-only on server side fo example), a NULL entry is still stored in unstableStorageFile. This cause any future WRITE calls to the same file to always fail, because COMMIT may not be invoked by the client.

This PR fix this issue by storing file pointer in unstableStorageFile only if not NULL.

@Toilal
Copy link
Contributor Author

Toilal commented Aug 30, 2017

@marcharding Do you think you will merge this quickly and release a new version of winnfsd and vagrant-plugin ?

@marcharding
Copy link
Member

I'll take a look later

@marcharding marcharding merged commit 26223f9 into winnfsd:master Aug 30, 2017
@marcharding
Copy link
Member

Hey looks good, thanks for fixing this.

I'll try and push a new vagrant plugin today or tomorrow.

@marcharding
Copy link
Member

hm, after a while the whole application freezes, this did not happen before

while the initial tests and the appveyor build looks ok, something is not quite right.

@Toilal Toilal deleted the access-denied-file-handle branch September 27, 2017 07:38
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

Successfully merging this pull request may close these issues.

2 participants