From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org, Juraj Marcin <jmarcin@redhat.com>,
Fabiano Rosas <farosas@suse.de>
Subject: Re: [PATCH for-10.1 0/2] migration: actually make gnutls workaround functional
Date: Mon, 29 Sep 2025 17:55:50 +0100 [thread overview]
Message-ID: <aNq6Fu0-nb1XMRxk@redhat.com> (raw)
In-Reply-To: <aNqsnaBkQe8i_MLK@x1.local>
On Mon, Sep 29, 2025 at 11:58:21AM -0400, Peter Xu wrote:
> On Fri, Aug 01, 2025 at 06:02:10PM +0100, Daniel P. Berrangé wrote:
> > 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(-)
>
> Dan, is there a planned repost on this one?
It is on my todo list, but I don't have a firm ETA yet.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2025-09-29 16:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-01 17:02 [PATCH for-10.1 0/2] migration: actually make gnutls workaround functional Daniel P. Berrangé
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é [this message]
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=aNq6Fu0-nb1XMRxk@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 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).