All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Pierre Morel <pmorel@linux.vnet.ibm.com>
Cc: virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] net/virtio-net: reverse unregistering on exit
Date: Tue, 22 Aug 2017 21:17:54 +0300	[thread overview]
Message-ID: <20170822211736-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <1503413992-29558-1-git-send-email-pmorel@linux.vnet.ibm.com>

On Tue, Aug 22, 2017 at 04:59:51PM +0200, Pierre Morel wrote:
> Hi,
> 
> I got a problem with virtio-net in a QEMU guest.
> 
> When virtio-net is used as a module in a guest and the network is
> activated, removing the virtio-net modules produces a kernel error:
> 
> [ 2375.624949] Last Breaking-Event-Address:
> [ 2375.624954]  [<00000000001453d4>] __cpuhp_remove_state+0x84/0x1a8
> [ 2375.624959] ---[ end trace cc9fd68b89f5235a ]---
> [ 2375.624966] Error: Removing state 163 which has instances left.
> [ 2375.624985] ------------[ cut here ]------------

Which kernel do you use?


> The problem is produced by an inversion in the order of unregistering
> the driver and the hotplug state machine callbacks in virtio_net_driver_exit.
> 
> This patch solves the problem by first unregistering the virtio_net_driver
> before unregistering the hotplug state machine callbacks.
> 
> Best regards,
> 
> Pierre Morel
> 
> Pierre Morel (1):
>   net/virtio-net: reverse unregistering on exit
> 
>  drivers/net/virtio_net.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> -- 
> 2.7.4

  parent reply	other threads:[~2017-08-22 18:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-22 14:59 [PATCH] net/virtio-net: reverse unregistering on exit Pierre Morel
2017-08-22 14:59 ` Pierre Morel
2017-08-22 18:13   ` Michael S. Tsirkin
2017-08-23  8:28     ` Pierre Morel
2017-08-22 18:17 ` Michael S. Tsirkin [this message]
2017-08-23  8:46   ` Pierre Morel

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=20170822211736-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=pmorel@linux.vnet.ibm.com \
    --cc=virtualization@lists.linux-foundation.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.