[Virtio-fs] [virtiofsd] Issue closed: Seccomp failure due to rseq

[virtiofs-bot at sinrega.org]

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:
1. Finding out which platforms the `rseq` syscall exists on,
2. Sending an appropriate patch to the `libc` crate,
3. Finding out on which targets glibc issues `rseq` so we know when to allow it in `src/seccomp.rs`.
---
https://gitlab.com/virtio-fs/virtiofsd/-/issues/34