* [Qemu-devel] [PATCH v2] Fix segfault on migration completion
@ 2011-10-28 16:59 Luiz Capitulino
2011-10-31 0:27 ` Juan Quintela
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: Luiz Capitulino @ 2011-10-28 16:59 UTC (permalink / raw)
To: qemu-devel; +Cc: Paolo Bonzini, Eduardo Habkost, Juan Jose Quintela Carreira
A simple migration reproduces it:
1. Start the source VM with:
# qemu [...] -S
2. Start the destination VM with:
# qemu <source VM cmd-line> -incoming tcp:0:4444
3. In the source VM:
(qemu) migrate -d tcp:0:4444
4. The source VM will segfault as soon as migration completes (might not
happen in the first try)
What is happening here is that qemu_file_put_notify() can end up closing
's->file' (in which case it's also set to NULL). The call stack is rather
complex, but Eduardo helped tracking it to:
select loop -> migrate_fd_put_notify() -> qemu_file_put_notify() ->
buffered_put_buffer() -> migrate_fd_put_ready() ->
migrate_fd_completed() -> migrate_fd_cleanup().
To be honest, it's not completely clear to me in which cases 's->file'
is not closed (on error maybe)? But I doubt this fix will make anything
worse.
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Acked-by: Eduardo Habkost <ehabkost@redhat.com>
Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
---
V2: better commit log
migration.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/migration.c b/migration.c
index bdca72e..f6e6208 100644
--- a/migration.c
+++ b/migration.c
@@ -252,7 +252,7 @@ static void migrate_fd_put_notify(void *opaque)
qemu_set_fd_handler2(s->fd, NULL, NULL, NULL, NULL);
qemu_file_put_notify(s->file);
- if (qemu_file_get_error(s->file)) {
+ if (s->file && qemu_file_get_error(s->file)) {
migrate_fd_error(s);
}
}
--
1.7.7.1.488.ge8e1c.dirty
^ permalink raw reply related [flat|nested] 4+ messages in thread
* Re: [Qemu-devel] [PATCH v2] Fix segfault on migration completion
2011-10-28 16:59 [Qemu-devel] [PATCH v2] Fix segfault on migration completion Luiz Capitulino
@ 2011-10-31 0:27 ` Juan Quintela
2011-10-31 6:15 ` Markus Armbruster
2011-11-01 18:04 ` Anthony Liguori
2 siblings, 0 replies; 4+ messages in thread
From: Juan Quintela @ 2011-10-31 0:27 UTC (permalink / raw)
To: Luiz Capitulino; +Cc: Paolo Bonzini, qemu-devel, Eduardo Habkost
Luiz Capitulino <lcapitulino@redhat.com> wrote:
> A simple migration reproduces it:
>
> 1. Start the source VM with:
>
> # qemu [...] -S
>
> 2. Start the destination VM with:
>
> # qemu <source VM cmd-line> -incoming tcp:0:4444
>
> 3. In the source VM:
>
> (qemu) migrate -d tcp:0:4444
>
> 4. The source VM will segfault as soon as migration completes (might not
> happen in the first try)
>
> What is happening here is that qemu_file_put_notify() can end up closing
> 's->file' (in which case it's also set to NULL). The call stack is rather
> complex, but Eduardo helped tracking it to:
>
> select loop -> migrate_fd_put_notify() -> qemu_file_put_notify() ->
> buffered_put_buffer() -> migrate_fd_put_ready() ->
> migrate_fd_completed() -> migrate_fd_cleanup().
>
> To be honest, it's not completely clear to me in which cases 's->file'
> is not closed (on error maybe)? But I doubt this fix will make anything
> worse.
>
> Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
> Acked-by: Eduardo Habkost <ehabkost@redhat.com>
> Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
> ---
>
> V2: better commit log
Acked-by: Juan Quintela <quintela@redhat.com>
And people wonder why error handling on migration is difficult, sniff
:-(
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Qemu-devel] [PATCH v2] Fix segfault on migration completion
2011-10-28 16:59 [Qemu-devel] [PATCH v2] Fix segfault on migration completion Luiz Capitulino
2011-10-31 0:27 ` Juan Quintela
@ 2011-10-31 6:15 ` Markus Armbruster
2011-11-01 18:04 ` Anthony Liguori
2 siblings, 0 replies; 4+ messages in thread
From: Markus Armbruster @ 2011-10-31 6:15 UTC (permalink / raw)
To: Luiz Capitulino
Cc: Paolo Bonzini, Juan Jose Quintela Carreira, qemu-devel,
Eduardo Habkost
Luiz Capitulino <lcapitulino@redhat.com> writes:
> A simple migration reproduces it:
>
> 1. Start the source VM with:
>
> # qemu [...] -S
>
> 2. Start the destination VM with:
>
> # qemu <source VM cmd-line> -incoming tcp:0:4444
>
> 3. In the source VM:
>
> (qemu) migrate -d tcp:0:4444
>
> 4. The source VM will segfault as soon as migration completes (might not
> happen in the first try)
>
> What is happening here is that qemu_file_put_notify() can end up closing
> 's->file' (in which case it's also set to NULL). The call stack is rather
> complex, but Eduardo helped tracking it to:
>
> select loop -> migrate_fd_put_notify() -> qemu_file_put_notify() ->
> buffered_put_buffer() -> migrate_fd_put_ready() ->
> migrate_fd_completed() -> migrate_fd_cleanup().
>
> To be honest, it's not completely clear to me in which cases 's->file'
> is not closed (on error maybe)? But I doubt this fix will make anything
> worse.
>
> Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
> Acked-by: Eduardo Habkost <ehabkost@redhat.com>
> Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
> ---
>
> V2: better commit log
>
> migration.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/migration.c b/migration.c
> index bdca72e..f6e6208 100644
> --- a/migration.c
> +++ b/migration.c
> @@ -252,7 +252,7 @@ static void migrate_fd_put_notify(void *opaque)
>
> qemu_set_fd_handler2(s->fd, NULL, NULL, NULL, NULL);
> qemu_file_put_notify(s->file);
> - if (qemu_file_get_error(s->file)) {
> + if (s->file && qemu_file_get_error(s->file)) {
> migrate_fd_error(s);
> }
> }
I wonder whether we can lose the error in s->file by closing s->file
before we get here. But even if we can, we still report more errors
than before the series this patch fixes.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Qemu-devel] [PATCH v2] Fix segfault on migration completion
2011-10-28 16:59 [Qemu-devel] [PATCH v2] Fix segfault on migration completion Luiz Capitulino
2011-10-31 0:27 ` Juan Quintela
2011-10-31 6:15 ` Markus Armbruster
@ 2011-11-01 18:04 ` Anthony Liguori
2 siblings, 0 replies; 4+ messages in thread
From: Anthony Liguori @ 2011-11-01 18:04 UTC (permalink / raw)
To: Luiz Capitulino
Cc: Paolo Bonzini, Juan Jose Quintela Carreira, qemu-devel,
Eduardo Habkost
On 10/28/2011 11:59 AM, Luiz Capitulino wrote:
> A simple migration reproduces it:
>
> 1. Start the source VM with:
>
> # qemu [...] -S
>
> 2. Start the destination VM with:
>
> # qemu<source VM cmd-line> -incoming tcp:0:4444
>
> 3. In the source VM:
>
> (qemu) migrate -d tcp:0:4444
>
> 4. The source VM will segfault as soon as migration completes (might not
> happen in the first try)
>
> What is happening here is that qemu_file_put_notify() can end up closing
> 's->file' (in which case it's also set to NULL). The call stack is rather
> complex, but Eduardo helped tracking it to:
>
> select loop -> migrate_fd_put_notify() -> qemu_file_put_notify() ->
> buffered_put_buffer() -> migrate_fd_put_ready() ->
> migrate_fd_completed() -> migrate_fd_cleanup().
>
> To be honest, it's not completely clear to me in which cases 's->file'
> is not closed (on error maybe)? But I doubt this fix will make anything
> worse.
>
> Reviewed-by: Paolo Bonzini<pbonzini@redhat.com>
> Acked-by: Eduardo Habkost<ehabkost@redhat.com>
> Signed-off-by: Luiz Capitulino<lcapitulino@redhat.com>
Applied. Thanks.
Regards,
Anthony Liguori
> ---
>
> V2: better commit log
>
> migration.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/migration.c b/migration.c
> index bdca72e..f6e6208 100644
> --- a/migration.c
> +++ b/migration.c
> @@ -252,7 +252,7 @@ static void migrate_fd_put_notify(void *opaque)
>
> qemu_set_fd_handler2(s->fd, NULL, NULL, NULL, NULL);
> qemu_file_put_notify(s->file);
> - if (qemu_file_get_error(s->file)) {
> + if (s->file&& qemu_file_get_error(s->file)) {
> migrate_fd_error(s);
> }
> }
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2011-11-01 18:04 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-10-28 16:59 [Qemu-devel] [PATCH v2] Fix segfault on migration completion Luiz Capitulino
2011-10-31 0:27 ` Juan Quintela
2011-10-31 6:15 ` Markus Armbruster
2011-11-01 18:04 ` Anthony Liguori
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).