qemu-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-commits] [qemu/qemu] 7b223e: tools/virtiofsd: Add rseq syscall to


From: Peter Maydell
Subject: [Qemu-commits] [qemu/qemu] 7b223e: tools/virtiofsd: Add rseq syscall to the seccomp a...
Date: Tue, 15 Feb 2022 14:41:13 -0800

  Branch: refs/heads/master
  Home:   https://github.com/qemu/qemu
  Commit: 7b223e38603de3a75602e14914d26f9d4baf52eb
      
https://github.com/qemu/qemu/commit/7b223e38603de3a75602e14914d26f9d4baf52eb
  Author: Christian Ehrhardt <christian.ehrhardt@canonical.com>
  Date:   2022-02-14 (Mon, 14 Feb 2022)

  Changed paths:
    M tools/virtiofsd/passthrough_seccomp.c

  Log Message:
  -----------
  tools/virtiofsd: Add rseq syscall to the seccomp allowlist

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>
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Message-id: 20220209111456.3328420-1-christian.ehrhardt@canonical.com

[Moved rseq to its alphabetically ordered position in the seccomp
allowlist.
--Stefan]
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>


  Commit: 34deee7b6a1418f3d62a91ff0a9d156e60a788a5
      
https://github.com/qemu/qemu/commit/34deee7b6a1418f3d62a91ff0a9d156e60a788a5
  Author: Dr. David Alan Gilbert <dgilbert@redhat.com>
  Date:   2022-02-14 (Mon, 14 Feb 2022)

  Changed paths:
    M docs/about/deprecated.rst

  Log Message:
  -----------
  Deprecate C virtiofsd

There's a nice new Rust implementation out there; recommend people
do new work on that.

Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Message-id: 20220210174714.19843-1-dgilbert@redhat.com
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>


  Commit: 4c41c69e05fe28c0f95f8abd2ebf407e95a4f04b
      
https://github.com/qemu/qemu/commit/4c41c69e05fe28c0f95f8abd2ebf407e95a4f04b
  Author: Hiroki Narukawa <hnarukaw@yahoo-corp.jp>
  Date:   2022-02-14 (Mon, 14 Feb 2022)

  Changed paths:
    M hw/block/virtio-blk.c
    M include/qemu/coroutine.h
    M util/qemu-coroutine.c

  Log Message:
  -----------
  util: adjust coroutine pool size to virtio block queue

Coroutine pool size was 64 from long ago, and the basis was organized in the 
commit message in 4d68e86b.

At that time, virtio-blk queue-size and num-queue were not configuable, and 
equivalent values were 128 and 1.

Coroutine pool size 64 was fine then.

Later queue-size and num-queue got configuable, and default values were 
increased.

Coroutine pool with size 64 exhausts frequently with random disk IO in new 
size, and slows down.

This commit adjusts coroutine pool size adaptively with new values.

This commit adds 64 by default, but now coroutine is not only for block devices,

and is not too much burdon comparing with new default.

pool size of 128 * vCPUs.

Signed-off-by: Hiroki Narukawa <hnarukaw@yahoo-corp.jp>
Message-id: 20220214115302.13294-2-hnarukaw@yahoo-corp.jp
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>


  Commit: ad38520bdeb2b1e0b487db317f29119e94c1c88d
      
https://github.com/qemu/qemu/commit/ad38520bdeb2b1e0b487db317f29119e94c1c88d
  Author: Peter Maydell <peter.maydell@linaro.org>
  Date:   2022-02-15 (Tue, 15 Feb 2022)

  Changed paths:
    M docs/about/deprecated.rst
    M hw/block/virtio-blk.c
    M include/qemu/coroutine.h
    M tools/virtiofsd/passthrough_seccomp.c
    M util/qemu-coroutine.c

  Log Message:
  -----------
  Merge remote-tracking branch 
'remotes/stefanha-gitlab/tags/block-pull-request' into staging

Pull request

This contains coroutine poll size scaling, virtiofsd rseq seccomp for new glibc
versions, and the QEMU C virtiofsd deprecation notice.

# gpg: Signature made Mon 14 Feb 2022 17:14:21 GMT
# gpg:                using RSA key 8695A8BFD3F97CDAAC35775A9CA4ABB381AB73C8
# gpg: Good signature from "Stefan Hajnoczi <stefanha@redhat.com>" [full]
# gpg:                 aka "Stefan Hajnoczi <stefanha@gmail.com>" [full]
# Primary key fingerprint: 8695 A8BF D3F9 7CDA AC35  775A 9CA4 ABB3 81AB 73C8

* remotes/stefanha-gitlab/tags/block-pull-request:
  util: adjust coroutine pool size to virtio block queue
  Deprecate C virtiofsd
  tools/virtiofsd: Add rseq syscall to the seccomp allowlist

Signed-off-by: Peter Maydell <peter.maydell@linaro.org>


Compare: https://github.com/qemu/qemu/compare/cc6721e449c4...ad38520bdeb2



reply via email to

[Prev in Thread] Current Thread [Next in Thread]