qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fabiano Rosas <farosas@suse.de>
To: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>,
	peterx@redhat.com
Cc: eblake@redhat.com, armbru@redhat.com, pbonzini@redhat.com,
	qemu-devel@nongnu.org, yc-core@yandex-team.ru
Subject: Re: [PATCH v3 4/4] qapi: introduce exit-on-error parameter for migrate-incoming
Date: Mon, 29 Apr 2024 10:06:47 -0300	[thread overview]
Message-ID: <87bk5s71y0.fsf@suse.de> (raw)
In-Reply-To: <3b6fe3da-04df-4cd1-a428-4b5cae11510a@yandex-team.ru>

Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru> writes:

> On 25.04.24 23:30, Fabiano Rosas wrote:
>>> @@ -797,13 +801,18 @@ fail:
>>>                         MIGRATION_STATUS_FAILED);
>>>       migration_incoming_state_destroy();
>>>   
>>> -    if (migrate_has_error(s)) {
>>> -        WITH_QEMU_LOCK_GUARD(&s->error_mutex) {
>>> -            error_report_err(s->error);
>>> +    if (mis->exit_on_error) {
>>> +        if (migrate_has_error(s)) {
>>> +            WITH_QEMU_LOCK_GUARD(&s->error_mutex) {
>>> +                error_report_err(s->error);
>> error_report_err(error_copy(s->error))
>> 
>> ...because later on you're reading from s->error at
>> fill_destination_migration_info.
>
> No, we immediately do exit() instead. That's just a preexisting behavior, moved into "if (mis->exit_on_error)"

I meant later in the patch, not later in the execution. Can't
query-migrate be called during process_incoming_migration_co?


  reply	other threads:[~2024-04-29 13:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-25 18:15 [PATCH v3 0/4] migration: do not exit on incoming failure Vladimir Sementsov-Ogievskiy
2024-04-25 18:15 ` [PATCH v3 1/4] migration: move trace-point from migrate_fd_error to migrate_set_error Vladimir Sementsov-Ogievskiy
2024-04-25 20:03   ` Fabiano Rosas
2024-04-25 18:15 ` [PATCH v3 2/4] migration: process_incoming_migration_co(): complete cleanup on failure Vladimir Sementsov-Ogievskiy
2024-04-25 20:03   ` Fabiano Rosas
2024-04-25 18:15 ` [PATCH v3 3/4] migration: process_incoming_migration_co(): rework error reporting Vladimir Sementsov-Ogievskiy
2024-04-25 20:21   ` Fabiano Rosas
2024-04-25 18:15 ` [PATCH v3 4/4] qapi: introduce exit-on-error parameter for migrate-incoming Vladimir Sementsov-Ogievskiy
2024-04-25 20:30   ` Fabiano Rosas
2024-04-29  7:45     ` Vladimir Sementsov-Ogievskiy
2024-04-29 13:06       ` Fabiano Rosas [this message]
2024-04-29 15:03         ` Vladimir Sementsov-Ogievskiy
2024-04-26  5:17   ` Markus Armbruster

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=87bk5s71y0.fsf@suse.de \
    --to=farosas@suse.de \
    --cc=armbru@redhat.com \
    --cc=eblake@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=vsementsov@yandex-team.ru \
    --cc=yc-core@yandex-team.ru \
    /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).