From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Thomas Huth <thuth@redhat.com>, armbru@redhat.com
Cc: kwolf@redhat.com,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-block@nongnu.org, armbru@redhat.com, qemu-devel@nongnu.org,
lcapitulino@redhat.com, mreitz@redhat.com,
Karen Mezick <kmezick@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] fix qmp-cont vs migration-finish race-crash
Date: Tue, 14 May 2019 17:20:17 +0100 [thread overview]
Message-ID: <20190514162016.GQ2753@work-vm> (raw)
In-Reply-To: <f92a06b5-6af6-dfe3-6e78-c4448e6a9cd0@redhat.com>
* Thomas Huth (thuth@redhat.com) wrote:
> On 24/01/2019 13.25, Vladimir Sementsov-Ogievskiy wrote:
> > Hi.
> >
> > It's a simple fix for problems reported in "Aborts in iotest 169"
> > by Max:
> > https://lists.gnu.org/archive/html/qemu-devel/2019-01/msg05907.html
> >
> > In thread Kevin described that a problem itself is bigger and needs
> > more effort:
> > https://lists.gnu.org/archive/html/qemu-devel/2019-01/msg06136.html
> >
> > So, we may continue discussion in "Aborts in iotest 169", and in
> > parallel apply these patches at least as a temporary fix.
> >
> > The problem of this fix is that we finally have a bit weird interface:
> >
> > User gets event MIGRATION_COMPLETED, and after it he can get error
> > message "Migration is not finalized yet".
> >
> > But it is better than crash, anyway.
> >
> > Vladimir Sementsov-Ogievskiy (2):
> > qmp: forbid qmp_cont in RUN_STATE_FINISH_MIGRATE
> > iotest: fix 169: do not run qmp_cont in RUN_STATE_FINISH_MIGRATE
>
> What happened to these two patches? As far as I can see, they've never
> got applied? Has another fix for 169 included instead?
Hmm not sure; they've slipped between the maintainers if not.
1/2 is a qmp.c so while it fixes a migration corner case it's probably
armbru that should take it.
Dave
> Thomas
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2019-05-14 16:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 12:25 [Qemu-devel] [PATCH 0/2] fix qmp-cont vs migration-finish race-crash Vladimir Sementsov-Ogievskiy
2019-01-24 12:25 ` [Qemu-devel] [PATCH 1/2] qmp: forbid qmp_cont in RUN_STATE_FINISH_MIGRATE Vladimir Sementsov-Ogievskiy
2019-01-24 13:38 ` Dr. David Alan Gilbert
2019-01-24 12:25 ` [Qemu-devel] [PATCH 2/2] iotest: fix 169: do not run " Vladimir Sementsov-Ogievskiy
2019-01-24 14:10 ` Vladimir Sementsov-Ogievskiy
2019-01-25 16:25 ` Max Reitz
2019-05-08 15:21 ` [Qemu-devel] [PATCH 0/2] fix qmp-cont vs migration-finish race-crash Thomas Huth
2019-05-14 16:20 ` Dr. David Alan Gilbert [this message]
2019-05-15 8:07 ` Kevin Wolf
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=20190514162016.GQ2753@work-vm \
--to=dgilbert@redhat.com \
--cc=armbru@redhat.com \
--cc=kmezick@redhat.com \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=vsementsov@virtuozzo.com \
/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).