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

On Android, use an explicit version check to detect openat2. #197

Merged
merged 1 commit into from
Nov 12, 2021

Conversation

sunfishcode
Copy link
Member

On Android, seccomp is configured to kill processes that execute
unsupported system calls, rather than returning ENOSYS, which
breaks the auto-detection code. So on Android, use an explicit
version check, using uname, to test whether the running kernel
supports openat2, before trying to call it.

On Android, seccomp is configured to kill processes that execute
unsupported system calls, rather than returning `ENOSYS`, which
breaks the auto-detection code. So on Android, use an explicit
version check, using `uname`, to test whether the running kernel
supports `openat2`, before trying to call it.
@sunfishcode sunfishcode force-pushed the sunfishcode/android-detect-openat2 branch from bee97d2 to d64564f Compare November 10, 2021 18:25
@hrydgard
Copy link

Works!

@sunfishcode
Copy link
Member Author

Thanks!

@sunfishcode sunfishcode merged commit 60c958f into main Nov 12, 2021
@sunfishcode sunfishcode deleted the sunfishcode/android-detect-openat2 branch November 12, 2021 14:57
sunfishcode added a commit that referenced this pull request Apr 10, 2023
Similar to #197, do a `uname` version check before using `statx` on
Android, since Android's seccomp configuration kills the process if any
unrecognized system calls are used.

Fixes #311.
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