qemu-devel
[Top][All Lists]
Advanced

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

[PULL 0/8] Misc fixes patches


From: Daniel P . Berrangé
Subject: [PULL 0/8] Misc fixes patches
Date: Tue, 19 Mar 2024 20:21:13 +0000

The following changes since commit c62d54d0a8067ffb3d5b909276f7296d7df33fa7:

  Update version for v9.0.0-rc0 release (2024-03-19 19:13:52 +0000)

are available in the Git repository at:

  https://gitlab.com/berrange/qemu tags/misc-fixes-pull-request

for you to fetch changes up to c3b1aa1c1ae66e0174704072b1fb7d10d6e4a4b7:

  crypto: report which ciphers are being skipped during tests (2024-03-19 
20:17:12 +0000)

----------------------------------------------------------------
 * Use EPERM for seccomp filter instead of killing QEMU when
   an attempt to spawn child process is made
 * Reduce priority of POLLHUP handling for socket chardevs
   to increase likelihood of pending data being processed
 * Fix chardev I/O main loop integration when TLS is enabled
 * Fix broken crypto test suite when distro disables
   SM4 algorithm
 * Improve diagnosis of failed crypto tests

----------------------------------------------------------------

Daniel P. Berrangé (8):
  seccomp: report EPERM instead of killing process for spawn set
  chardev: lower priority of the HUP GSource in socket chardev
  Revert "chardev/char-socket: Fix TLS io channels sending too much data
    to the backend"
  Revert "chardev: use a child source for qio input source"
  crypto: factor out conversion of QAPI to gcrypt constants
  crypto: query gcrypt for cipher availability
  crypto: use error_abort for unexpected failures
  crypto: report which ciphers are being skipped during tests

 chardev/char-io.c               |  56 +++++++++++++--
 chardev/char-socket.c           |  22 +++++-
 crypto/cipher-gcrypt.c.inc      | 121 +++++++++++++++++---------------
 system/qemu-seccomp.c           |  10 +--
 tests/unit/test-crypto-cipher.c |   7 +-
 5 files changed, 145 insertions(+), 71 deletions(-)

-- 
2.43.0




reply via email to

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