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
_______________________________________________ Virtio-fs mailing list Virtio-fs@redhat.com https://listman.redhat.com/mailman/listinfo/virtio-fs
