From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: [PULL 0/8] Misc fixes patches
Date: Tue, 19 Mar 2024 20:21:13 +0000 [thread overview]
Message-ID: <20240319202121.233130-1-berrange@redhat.com> (raw)
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
next reply other threads:[~2024-03-19 20:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 20:21 Daniel P. Berrangé [this message]
2024-03-19 20:21 ` [PULL 1/8] seccomp: report EPERM instead of killing process for spawn set Daniel P. Berrangé
2024-03-19 20:21 ` [PULL 2/8] chardev: lower priority of the HUP GSource in socket chardev Daniel P. Berrangé
2024-03-19 20:21 ` [PULL 3/8] Revert "chardev/char-socket: Fix TLS io channels sending too much data to the backend" Daniel P. Berrangé
2024-03-19 20:21 ` [PULL 4/8] Revert "chardev: use a child source for qio input source" Daniel P. Berrangé
2024-03-19 20:21 ` [PULL 5/8] crypto: factor out conversion of QAPI to gcrypt constants Daniel P. Berrangé
2024-03-19 20:21 ` [PULL 6/8] crypto: query gcrypt for cipher availability Daniel P. Berrangé
2024-03-19 20:21 ` [PULL 7/8] crypto: use error_abort for unexpected failures Daniel P. Berrangé
2024-03-19 20:21 ` [PULL 8/8] crypto: report which ciphers are being skipped during tests Daniel P. Berrangé
2024-03-20 15:04 ` [PULL 0/8] Misc fixes patches Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2026-10-16 9:43 Daniel P. Berrangé
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=20240319202121.233130-1-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.