-
Notifications
You must be signed in to change notification settings - Fork 666
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
unistd: add execveat() on Linux and Android #800
Conversation
c5feda5
to
4741e4f
Compare
I had to constrain Linux tests to x86 and amd64 only, as travis was failing with |
Please s/Linus/Linux in the commit message. |
This adds execveat() to `nix::unistd`. It uses the execveat(2) Linux kernel syscall, which is available since 3.19. This is a Linux-specific extension which is not covered by POSIX and does not have any userland libc wrapper. Ref: http://man7.org/linux/man-pages/man2/execveat.2.html
Woops for the typo. I rebased to fix that and to resolve a conflict on the changelog, PTAL. No, I didn't explicitly test this on Android as I don't have at hand an environment for that. |
I don't have an Android test environment either. But it looks correct and Android is only Tier 2, so it's ok to merge. |
Ack. May I then get a review and merge? Or is there anything else I can do here? |
800: unistd: add execveat() on Linux and Android r=Susurrus a=lucab This adds execveat() to `nix::unistd`. It uses the execveat(2) Linux kernel syscall, which is available since 3.19. This is a Linux-specific extension which is not covered by POSIX and does not have any userland libc wrapper. Ref: http://man7.org/linux/man-pages/man2/execveat.2.html
This adds execveat() to
nix::unistd
. It uses the execveat(2) Linuxkernel syscall, which is available since 3.19.
This is a Linux-specific extension which is not covered by POSIX and
does not have any userland libc wrapper.
Ref: http://man7.org/linux/man-pages/man2/execveat.2.html