diff options
| author | Peter Xu <peterx@redhat.com> | 2025-09-18 16:39:37 -0400 |
|---|---|---|
| committer | Peter Xu <peterx@redhat.com> | 2025-10-03 09:48:02 -0400 |
| commit | dc487044d5c09d32dd19c8e85e76396fbbc9dde1 (patch) | |
| tree | 7736a2add6114125532afd5cae73b7f080ca9c0a /scripts/lib/kdoc/kdoc_output.py | |
| parent | 7e0c22d585581b8083ffdeb332ea497218665daf (diff) | |
| download | qemu-dc487044d5c09d32dd19c8e85e76396fbbc9dde1.zip qemu-dc487044d5c09d32dd19c8e85e76396fbbc9dde1.tar.gz qemu-dc487044d5c09d32dd19c8e85e76396fbbc9dde1.tar.bz2 | |
migration: Make migration_has_failed() work even for CANCELLING
No issue I hit, the change is only from code observation when I am looking
at a TLS premature termination issue.
We set CANCELLED very late, it means migration_has_failed() may not work
correctly if it's invoked before updating CANCELLING to CANCELLED.
Allow that state will make migration_has_failed() working as expected even
if it's invoked slightly earlier.
One current user is the multifd code for the TLS graceful termination,
where it's before updating to CANCELLED.
Reviewed-by: Juraj Marcin <jmarcin@redhat.com>
Reviewed-by: Fabiano Rosas <farosas@suse.de>
Link: https://lore.kernel.org/r/20250918203937.200833-3-peterx@redhat.com
Signed-off-by: Peter Xu <peterx@redhat.com>
Diffstat (limited to 'scripts/lib/kdoc/kdoc_output.py')
0 files changed, 0 insertions, 0 deletions
