netvsc: use RCU to protect inner device structure
authorstephen hemminger <stephen@networkplumber.org>
Wed, 22 Mar 2017 21:51:00 +0000 (14:51 -0700)
committerDavid S. Miller <davem@davemloft.net>
Thu, 23 Mar 2017 02:38:56 +0000 (19:38 -0700)
commit545a8e79bd1cc8774877a26275171a2ec8881c9e
treeb3e0a7cb5aa7d38dd61fa76c93bdf2cc7e0b2906
parent3071ada4916e26a8961c1b99f7766a73b9007bfc
netvsc: use RCU to protect inner device structure

The netvsc driver has an internal structure (netvsc_device) which
is created when device is opened and released when device is closed.
And also opened/released when MTU or number of channels change.

Since this is referenced in the receive and transmit path, it is
safer to use RCU to protect/prevent use after free problems.

Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
drivers/net/hyperv/hyperv_net.h
drivers/net/hyperv/netvsc.c
drivers/net/hyperv/netvsc_drv.c