Android SECCOMP forbids accept4 on x86

[jshearer]

It appears that when running native code on Android x86 (such as in the emulator), the seccomp profile forbids syscall 364 which maps to accept4. Would a PR to include android x86 in the list of targets that get accept instead of accept4 be approved?

01-24 14:43:55.326 18621 18621 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
01-24 14:43:55.326 18621 18621 F DEBUG   : Build fingerprint: 'google/sdk_gphone_x86/generic_x86:10/QSR1.200715.002/6695061:userdebug/dev-keys'
01-24 14:43:55.326 18621 18621 F DEBUG   : Revision: '0'
01-24 14:43:55.326 18621 18621 F DEBUG   : ABI: 'x86'
01-24 14:43:55.328 18621 18621 F DEBUG   : Timestamp: 2021-01-24 14:43:55-0500
01-24 14:43:55.328 18621 18621 F DEBUG   : pid: 18525, tid: 18607, name: tokio-runtime-w  >>> com.xxx <<<
01-24 14:43:55.328 18621 18621 F DEBUG   : uid: 10134
01-24 14:43:55.328 18621 18621 F DEBUG   : signal 31 (SIGSYS), code 1 (SYS_SECCOMP), fault addr --------
01-24 14:43:55.328 18621 18621 F DEBUG   : Cause: seccomp prevented call to disallowed x86 system call 364
01-24 14:43:55.328 18621 18621 F DEBUG   :     eax 0000016c  ebx 00000066  ecx b4c5b3d0  edx b4c5b3cc
01-24 14:43:55.328 18621 18621 F DEBUG   :     edi d233b034  esi 00080800
01-24 14:43:55.328 18621 18621 F DEBUG   :     ebp bcbd2e48  esp b4c5b378  eip ed8b4ef9
01-24 14:43:55.331 18621 18621 F DEBUG   :
01-24 14:43:55.331 18621 18621 F DEBUG   : backtrace:
01-24 14:43:55.331 18621 18621 F DEBUG   :       #00 pc 00000ef9  [vdso] (__kernel_vsyscall+9)
01-24 14:43:55.331 18621 18621 F DEBUG   :       #01 pc 00092328  /apex/com.android.runtime/lib/bionic/libc.so (syscall+40) (BuildId: 471745f0fbbcedb3db1553d5bd6fcd8b)
01-24 14:43:55.331 18621 18621 F DEBUG   :       #02 pc 02b4cadf  /data/app/com.xxx-XUlpEulmSi9ahcxULGtS2Q==/lib/x86/libmy_special_library.so (offset 0xe35000)