Skip to content

Conversation

kripken
Copy link
Member

@kripken kripken commented Feb 15, 2022

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:

  • Add FS.chmod
  • Fix FS.mkdir which did not receive or sent the mode param to wasm
  • Implement __syscall_fstatat64

@kripken kripken requested review from sbc100 and tlively February 15, 2022 18:31
return 0;
}

long __syscall_access(long path, long amode) {
Copy link
Collaborator

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...

Copy link
Collaborator

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

Copy link
Member Author

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.

@kripken
Copy link
Member Author

kripken commented Feb 15, 2022

Ok, after #16296 this is now much simpler. It just:

  • Add FS.chmod
  • Fix FS.mkdir which did not receive or sent the mode param to wasm
  • Test tweaks and enable testing of test_unistd_access

@kripken kripken merged commit 4a72bc3 into main Feb 15, 2022
@kripken kripken deleted the wfnext branch February 15, 2022 23:43
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.

3 participants