-
Notifications
You must be signed in to change notification settings - Fork 3.4k
[WasmFS] Implement __syscall_faccessat #16295
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
Conversation
system/lib/wasmfs/syscalls.cpp
Outdated
return 0; | ||
} | ||
|
||
long __syscall_access(long path, long amode) { |
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.
It seems odd that we would want/need to support both of the syscalls...
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.
I looks like we can/should make PR to remove our definition of __syscall_access so musl will just use __syscall_accessat
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.
Ok, I'll try that.
Ok, after #16296 this is now much simpler. It just:
|
Implement
__syscall_faccessat
. It is basically the same as the existing__syscall_access
except it has two more flags.To get the test passing, also:
FS.chmod
FS.mkdir
which did not receive or sent the mode param to wasm__syscall_fstatat64