All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Vivier <lvivier@redhat.com>
To: Jason Wang <jasowang@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Igor Mammedov <imammedo@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH] virtio-net: failover: add missing remove_migration_state_change_notifier()
Date: Wed, 5 May 2021 09:46:14 +0200	[thread overview]
Message-ID: <73e2fa26-b7d8-ad29-b9e9-4885a526882e@redhat.com> (raw)
In-Reply-To: <2387a23c-667c-d905-0058-51e48f9be2f4@redhat.com>

On 29/04/2021 09:26, Jason Wang wrote:
> 
> 在 2021/4/28 下午6:14, Michael S. Tsirkin 写道:
>> On Tue, Apr 27, 2021 at 03:02:34PM +0100, Dr. David Alan Gilbert wrote:
>>> * Laurent Vivier (lvivier@redhat.com) wrote:
>>>> In the failover case configuration, virtio_net_device_realize() uses an
>>>> add_migration_state_change_notifier() to add a state notifier, but this
>>>> notifier is not removed by the unrealize function when the virtio-net
>>>> card is unplugged.
>>>>
>>>> If the card is unplugged and a migration is started, the notifier is
>>>> called and as it is not valid anymore QEMU crashes.
>>>>
>>>> This patch fixes the problem by adding the
>>>> remove_migration_state_change_notifier() in virtio_net_device_unrealize().
>>>>
>>>> The problem can be reproduced with:
>>>>
>>>>    $ qemu-system-x86_64 -enable-kvm -m 1g -M q35 \
>>>>      -device pcie-root-port,slot=4,id=root1 \
>>>>      -device pcie-root-port,slot=5,id=root2 \
>>>>      -device virtio-net-pci,id=net1,mac=52:54:00:6f:55:cc,failover=on,bus=root1 \
>>>>      -monitor stdio disk.qcow2
>>>>    (qemu) device_del net1
>>>>    (qemu) migrate "exec:gzip -c > STATEFILE.gz"
>>>>
>>>>    Thread 1 "qemu-system-x86" received signal SIGSEGV, Segmentation fault.
>>>>    0x0000000000000000 in ?? ()
>>>>    (gdb) bt
>>>>    #0  0x0000000000000000 in  ()
>>>>    #1  0x0000555555d726d7 in notifier_list_notify (...)
>>>>        at .../util/notify.c:39
>>>>    #2  0x0000555555842c1a in migrate_fd_connect (...)
>>>>        at .../migration/migration.c:3975
>>>>    #3  0x0000555555950f7d in migration_channel_connect (...)
>>>>        error@entry=0x0) at .../migration/channel.c:107
>>>>    #4  0x0000555555910922 in exec_start_outgoing_migration (...)
>>>>        at .../migration/exec.c:42
>>>>
>>>> Reported-by: Igor Mammedov <imammedo@redhat.com>
>>>> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
>>> Yep, I think that's OK.
>>>
>>>
>>> Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
>> Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
>>
>> net stuff so I expect Jason will merge this ...
> 
> 
> Ok, I've queued this.

Thank you.

Any idea when the PR will be sent?

Thanks,
Laurent



  reply	other threads:[~2021-05-05  7:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-27 13:51 [PATCH] virtio-net: failover: add missing remove_migration_state_change_notifier() Laurent Vivier
2021-04-27 14:02 ` Dr. David Alan Gilbert
2021-04-27 14:16   ` Philippe Mathieu-Daudé
2021-04-28 10:14   ` Michael S. Tsirkin
2021-04-29  7:26     ` Jason Wang
2021-05-05  7:46       ` Laurent Vivier [this message]
2021-05-06  3:30         ` Jason Wang
2021-04-28  2:28 ` Jason Wang

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=73e2fa26-b7d8-ad29-b9e9-4885a526882e@redhat.com \
    --to=lvivier@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=mst@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.