From: Juergen Gross <jgross@suse.com>
To: Eduardo Otubo <otubo@redhat.com>, xen-devel@lists.xenproject.org
Cc: netdev@vger.kernel.org, paul.durrant@citrix.com,
wei.liu2@citrix.com, linux-kernel@vger.kernel.org,
vkuznets@redhat.com, cavery@redhat.com, cheshi@redhat.com,
mgamal@redhat.com, boris.ostrovsky@oracle.com
Subject: Re: [PATCHv2] xen-netfront: remove warning when unloading module
Date: Mon, 27 Nov 2017 10:00:46 +0100 [thread overview]
Message-ID: <74dc58e4-5317-f864-dcf5-c2b283744930@suse.com> (raw)
In-Reply-To: <20171123141835.5820-1-otubo@redhat.com>
On 23/11/17 15:18, Eduardo Otubo wrote:
> v2:
> * Replace busy wait with wait_event()/wake_up_all()
> * Cannot garantee that at the time xennet_remove is called, the
> xen_netback state will not be XenbusStateClosed, so added a
> condition for that
> * There's a small chance for the xen_netback state is
> XenbusStateUnknown by the time the xen_netfront switches to Closed,
> so added a condition for that.
>
> When unloading module xen_netfront from guest, dmesg would output
> warning messages like below:
>
> [ 105.236836] xen:grant_table: WARNING: g.e. 0x903 still in use!
> [ 105.236839] deferring g.e. 0x903 (pfn 0x35805)
>
> This problem relies on netfront and netback being out of sync. By the time
> netfront revokes the g.e.'s netback didn't have enough time to free all of
> them, hence displaying the warnings on dmesg.
>
> The trick here is to make netfront to wait until netback frees all the g.e.'s
> and only then continue to cleanup for the module removal, and this is done by
> manipulating both device states.
>
> Signed-off-by: Eduardo Otubo <otubo@redhat.com>
Acked-by: Juergen Gross <jgross@suse.com>
Juergen
next prev parent reply other threads:[~2017-11-27 9:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 14:18 Eduardo Otubo
2017-11-27 9:00 ` Juergen Gross [this message]
2017-11-27 19:22 ` David Miller
2018-01-31 15:00 ` [Xen-devel] " Oleksandr Andrushchenko
2018-02-02 8:54 ` Eduardo Otubo
2018-02-02 9:45 ` Oleksandr Andrushchenko
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=74dc58e4-5317-f864-dcf5-c2b283744930@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=cavery@redhat.com \
--cc=cheshi@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgamal@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=otubo@redhat.com \
--cc=paul.durrant@citrix.com \
--cc=vkuznets@redhat.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®