From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: christian.ehrhardt@canonical.com
Cc: qemu-devel <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
Michael Hudson-Doyle <michael.hudson@canonical.com>
Subject: Re: [PATCH] tools/virtiofsd: Add rseq syscall to the seccomp allowlist
Date: Wed, 9 Feb 2022 12:49:42 +0000 [thread overview]
Message-ID: <YgO4ZrshcZAXP9z6@work-vm> (raw)
In-Reply-To: <20220209111456.3328420-1-christian.ehrhardt@canonical.com>
* christian.ehrhardt@canonical.com (christian.ehrhardt@canonical.com) wrote:
> From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
>
> The virtiofsd currently crashes when used with glibc 2.35.
> That is due to the rseq system call being added to every thread
> creation [1][2].
>
> [1]: https://www.efficios.com/blog/2019/02/08/linux-restartable-sequences/
> [2]: https://sourceware.org/pipermail/libc-alpha/2022-February/136040.html
>
> This happens not at daemon start, but when a guest connects
>
> /usr/lib/qemu/virtiofsd -f --socket-path=/tmp/testvfsd -o sandbox=chroot \
> -o source=/var/guests/j-virtiofs --socket-group=kvm
> virtio_session_mount: Waiting for vhost-user socket connection...
> # start ok, now guest will connect
> virtio_session_mount: Received vhost-user socket connection
> virtio_loop: Entry
> fv_queue_set_started: qidx=0 started=1
> fv_queue_set_started: qidx=1 started=1
> Bad system call (core dumped)
>
> We have to put rseq on the seccomp allowlist to avoid that the daemon
> is crashing in this case.
>
> Reported-by: Michael Hudson-Doyle <michael.hudson@canonical.com>
> Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Thanks! I bet this is going to pop up in zillions of programs.
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> ---
> tools/virtiofsd/passthrough_seccomp.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/tools/virtiofsd/passthrough_seccomp.c b/tools/virtiofsd/passthrough_seccomp.c
> index a3ce9f898d..21b8f53bd9 100644
> --- a/tools/virtiofsd/passthrough_seccomp.c
> +++ b/tools/virtiofsd/passthrough_seccomp.c
> @@ -116,6 +116,9 @@ static const int syscall_allowlist[] = {
> SCMP_SYS(write),
> SCMP_SYS(writev),
> SCMP_SYS(umask),
> +#ifdef __NR_rseq
> + SCMP_SYS(rseq), /* required since glibc 2.35 */
> +#endif
> };
>
> /* Syscalls used when --syslog is enabled */
> --
> 2.35.0
>
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2022-02-09 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 11:14 [PATCH] tools/virtiofsd: Add rseq syscall to the seccomp allowlist christian.ehrhardt
2022-02-09 12:49 ` Dr. David Alan Gilbert [this message]
2022-02-09 15:13 ` Stefan Hajnoczi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YgO4ZrshcZAXP9z6@work-vm \
--to=dgilbert@redhat.com \
--cc=christian.ehrhardt@canonical.com \
--cc=michael.hudson@canonical.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).