From: Fabiano Rosas <farosas@suse.de>
To: Peter Xu <peterx@redhat.com>, qemu-devel@nongnu.org
Cc: "Juraj Marcin" <jmarcin@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
peterx@redhat.com
Subject: Re: [PATCH v2 1/3] io/crypto: Move tls premature termination handling into QIO layer
Date: Thu, 18 Sep 2025 11:12:39 -0300 [thread overview]
Message-ID: <87ecs3voh4.fsf@suse.de> (raw)
In-Reply-To: <20250911212355.1943494-2-peterx@redhat.com>
Peter Xu <peterx@redhat.com> writes:
> QCryptoTLSSession allows TLS premature termination in two cases, one of the
> case is when the channel shutdown() is invoked on READ side.
>
> It's possible the shutdown() happened after the read thread blocked at
> gnutls_record_recv(). In this case, we should allow the premature
> termination to happen.
>
> The problem is by the time qcrypto_tls_session_read() was invoked,
> tioc->shutdown may not have been set, so this may instead be treated as an
> error if there is concurrent shutdown() calls.
>
> To allow the flag to reflect the latest status of tioc->shutdown, move the
> check upper into the QIOChannel level, so as to read the flag only after
> QEMU gets an GNUTLS_E_PREMATURE_TERMINATION.
>
> When at it, introduce qio_channel_tls_allow_premature_termination() helper
> to make the condition checks easier to read.
>
> This patch will fix a qemu qtest warning when running the preempt tls test,
> reporting premature termination:
>
> QTEST_QEMU_BINARY=./qemu-system-x86_64 ./tests/qtest/migration-test --full -r /x86_64/migration/postcopy/preempt/tls/psk
> ...
> qemu-kvm: Cannot read from TLS channel: The TLS connection was non-properly terminated.
> ...
>
> In this specific case, the error was set by postcopy_preempt_thread, which
> normally will be concurrently shutdown()ed by the main thread.
>
> Signed-off-by: Peter Xu <peterx@redhat.com>
Reviewed-by: Fabiano Rosas <farosas@suse.de>
next prev parent reply other threads:[~2025-09-18 14:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 21:23 [PATCH v2 0/3] migration/tls: Graceful shutdowns for main and postcopy channels Peter Xu
2025-09-11 21:23 ` [PATCH v2 1/3] io/crypto: Move tls premature termination handling into QIO layer Peter Xu
2025-09-12 11:18 ` Daniel P. Berrangé
2025-09-12 15:24 ` Peter Xu
2025-09-15 18:31 ` Daniel P. Berrangé
2025-09-12 12:05 ` Juraj Marcin
2025-09-18 14:12 ` Fabiano Rosas [this message]
2025-09-11 21:23 ` [PATCH v2 2/3] io/tls: Make qio_channel_tls_bye() always synchronous Peter Xu
2025-09-12 11:27 ` Daniel P. Berrangé
2025-09-12 15:36 ` Peter Xu
2025-09-15 18:40 ` Daniel P. Berrangé
2025-09-15 20:41 ` Peter Xu
2025-09-18 14:47 ` Fabiano Rosas
2025-09-18 18:12 ` Peter Xu
2025-09-11 21:23 ` [PATCH v2 3/3] migration: Make migration_has_failed() work even for CANCELLING Peter Xu
2025-09-12 12:07 ` Juraj Marcin
2025-09-18 14:52 ` Fabiano Rosas
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=87ecs3voh4.fsf@suse.de \
--to=farosas@suse.de \
--cc=berrange@redhat.com \
--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.