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

update WASI fs abstraction to open files on each rw #448

Closed
wants to merge 1 commit into from

Conversation

MarkMcCaskey
Copy link
Contributor

resolves #438

It's unclear whether this change is a good idea or not.

I'll have to look in to it some more. Additionally, this PR could break existing code, we should test it

@MarkMcCaskey MarkMcCaskey added the 📦 lib-wasi About wasmer-wasi label May 15, 2019
@MarkMcCaskey
Copy link
Contributor Author

We can always add an optimization here, having an Option<File> in WasiFile::HostFile to avoid forcing disk synchronization/opening and closing the same files over and over.

My intuition is that the solution as is has an unacceptable performance impact

@MarkMcCaskey
Copy link
Contributor Author

closing in favor of #449

@MarkMcCaskey MarkMcCaskey deleted the feature/keep-files-closed-wasi branch May 15, 2019 22:13
bors bot added a commit that referenced this pull request May 15, 2019
449: avoid opening files when not needed in WASI, check for write permissions r=MarkMcCaskey a=MarkMcCaskey

resolves #438 

Follow up to  #448.  Turns out we don't have to complect things in that way, we can just be more conservative about opening files and granting write permissions

Co-authored-by: Mark McCaskey <mark@wasmer.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📦 lib-wasi About wasmer-wasi
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Likely unnecessary write access to a file
1 participant