Skip ENOSYS filter in numa init

[am11]

The usage of get_mempolicy is restricted by secomp profile in docker. I couldn't figure out way to repro it with SELinux (class labels are confusing), but docker approach is fine.

It was fixed in libnuma a few days ago numactl/numactl@0efea0e so it's not a huge issue.

Fix #110074

[janvorli]

LGTM, thank you!

[janvorli]

Actually, I am not sure if it is causing the crash in the #110074. The rest of the code in the function should still work and not crash. Since that crash happens on HarmonyOS, I wonder if the crash could occur in the syscall itself due to mishandling of the mode argument being NULL.

[am11]

I was trying to repro it on Fedora VM with SELinux enabled, that operation not permitted is a bit tricky to reproduce since there is no class label for syscall (https://selinuxproject.org/page/ObjectClassesPerms#Kernel_Object_Classes) and my experiments were failing. With seccomp CAP_SYS_NICE, it's possible to make get_mempolicy syscall fail with EPERM. This change itself is aligning with the recent libnuma behavior. Also, from syscall(2) manpage:

ENOSYS The requested system call number is not implemented. Other errors are specific to the invoked system call.