Usage of sched_setattr
OS: Arch Linux glib: 2.64.5 glibc: 2.32
Using glib in applications sandboxed by seccomp, the sched_setattr and sched_getattr syscalls seem to be required by default even though the application itself does not utilize this system call.
If the syscall is not allowed, it results in the following error:
GLib-CRITICAL **: 15:42:27.083: Failed to set scheduler settings: Operation not permitted
A related issue was documented here: #2039 (closed)
If I understand correctly, this syscall can be used by some features of glib. My question is if this syscall needs to be used by default (maybe for checking) or if this is unintended. Is it possible to avoid using sched_setattr somehow?