All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Juraj Marcin" <jmarcin@redhat.com>,
	"Peter Xu" <peterx@redhat.com>, "Fabiano Rosas" <farosas@suse.de>,
	"Daniel P. Berrangé" <berrange@redhat.com>
Subject: [PATCH for-10.1 0/2] migration: actually make gnutls workaround functional
Date: Fri,  1 Aug 2025 18:02:10 +0100	[thread overview]
Message-ID: <20250801170212.54409-1-berrange@redhat.com> (raw)

This is a followup to previously merged patches that claimed to
workaround the gnutls bug impacting migration, but in fact were
essentially non-functional. Juraj Marcin pointed this out, and
this new patch tweaks the workaround to make it actually do
something useful.

Daniel P. Berrangé (2):
  migration: simplify error reporting after channel read
  migration: fix workaround for gnutls thread safety

 crypto/tlssession.c   | 16 ----------------
 migration/qemu-file.c | 22 +++++++++++++++++-----
 2 files changed, 17 insertions(+), 21 deletions(-)

-- 
2.50.1



             reply	other threads:[~2025-08-01 18:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-01 17:02 Daniel P. Berrangé [this message]
2025-08-01 17:02 ` [PATCH 1/2] migration: simplify error reporting after channel read Daniel P. Berrangé
2025-08-04 10:18   ` Prasad Pandit
2025-08-04 10:22     ` Daniel P. Berrangé
2025-08-04 11:03       ` Prasad Pandit
2025-08-06  0:41   ` Peter Xu
2025-08-01 17:02 ` [PATCH 2/2] migration: fix workaround for gnutls thread safety Daniel P. Berrangé
2025-08-04 10:29   ` Prasad Pandit
2025-08-04 18:13   ` Fabiano Rosas
2025-08-04 17:53 ` [PATCH for-10.1 0/2] migration: actually make gnutls workaround functional Juraj Marcin
2025-08-04 19:27   ` Fabiano Rosas
2025-08-05 10:09     ` Daniel P. Berrangé
2025-08-05 13:44       ` Fabiano Rosas
2025-08-05 14:18         ` Daniel P. Berrangé
2025-08-05 15:28           ` Fabiano Rosas
2025-08-05 14:52         ` Juraj Marcin
2025-08-06 14:54           ` Peter Xu
2025-09-29 15:58 ` Peter Xu
2025-09-29 16:55   ` Daniel P. Berrangé
2025-09-29 17:31     ` Peter Xu

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=20250801170212.54409-1-berrange@redhat.com \
    --to=berrange@redhat.com \
    --cc=farosas@suse.de \
    --cc=jmarcin@redhat.com \
    --cc=peterx@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.