Seccomp failure due to rseq
It seems that glibc has as of the 2.35 release begun using the (new?) rseq
syscall (see https://savannah.gnu.org/forum/forum.php?forum_id=10111), so I believe we need to add it to src/seccomp.rs
’s allowlist. Now, if I knew how, I’d’ve already sent a patch; but the libc
crate does not seem to have libc::SYS_rseq
, so I don’t know how.
Thus, I’m opening this issue hoping that someone has a simpler idea than:
- Finding out which platforms the
rseq
syscall exists on, - Sending an appropriate patch to the
libc
crate, - Finding out on which targets glibc issues
rseq
so we know when to allow it insrc/seccomp.rs
.