We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Problem description locate exits prematurely on Android Pie
locate
Steps to reproduce
$ locate -S Bad system call $ echo $? 159
Additional information strace reveals that setgid() is triggering seccomp
strace
22579 getgid() = 10313 22579 setgid(10313) = 10313 22579 --- SIGSYS {si_signo=31 /* SIGSYS */, si_code=0x1 /* SYS_SECCOMP */, si_call_addr=0x7d49a3313c, si_syscall=__NR_setgid, si_arch=0xc00000b7 /* AUDIT_ARCH_AARCH64 */} --- 22579 rt_sigaction(31 /* SIGSYS */, NULL, {sa_handler=0x7d49cb1094, sa_mask=~[KILL STOP RTMIN RT_1 RT_2 RT_3], sa_flags=0x18000004 /* SA_ONSTACK|SA_RESTART|SA_SIGINFO */}, 8) = 0
Below is the partial output of command termux-info.
termux-info
Updatable packages: All packages up to date Subscribed repositories: https://dl.bintray.com/xeffyr/unstable-packages-24 unstable/main https://dl.bintray.com/grimler/termux-root-packages-24 root/stable https://dl.bintray.com/termux/termux-packages-24 stable/main System information: Linux localhost 4.9.106-perf+ #1 SMP PREEMPT Wed Apr 3 22:25:17 CST 2019 aarch64 Android Termux-packages arch: aarch64 Android version: 9
A similar issue with screen was patched at fb83a47
screen
The text was updated successfully, but these errors were encountered:
mlocate: avoid using setgid
32deb4a
Fixes #3824
Successfully merging a pull request may close this issue.
Problem description
locate
exits prematurely on Android PieSteps to reproduce
Additional information
strace
reveals that setgid() is triggering seccompBelow is the partial output of command
termux-info
.A similar issue with
screen
was patched at fb83a47The text was updated successfully, but these errors were encountered: