summaryrefslogtreecommitdiffstats
path: root/net
diff options
context:
space:
mode:
authorEduardo Otubo <otubo@redhat.com>2017-11-23 15:18:35 +0100
committerDavid S. Miller <davem@davemloft.net>2017-11-27 14:21:58 -0500
commit5b5971df3bc2775107ddad164018a8a8db633b81 (patch)
treedca1b7578a39cd189f67e2feba7d49d54ade1adc /net
parentd3fe1e0185cffabc9b6f73f246a5552b46af7131 (diff)
downloadlinux-stable-5b5971df3bc2775107ddad164018a8a8db633b81.tar.gz
linux-stable-5b5971df3bc2775107ddad164018a8a8db633b81.tar.bz2
linux-stable-5b5971df3bc2775107ddad164018a8a8db633b81.zip
xen-netfront: remove warning when unloading module
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> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions