Vitaly Kuznetsov d072218f21 hv_netvsc: avoid deadlocks between rtnl lock and vf_use_cnt wait
Here is a deadlock scenario:
- netvsc_vf_up() schedules netvsc_notify_peers() work and quits.
- netvsc_vf_down() runs before netvsc_notify_peers() gets executed. As it
  is being executed from netdev notifier chain we hold rtnl lock when we
  get here.
- we enter while (atomic_read(&net_device_ctx->vf_use_cnt) != 0) loop and
  wait till netvsc_notify_peers() drops vf_use_cnt.
- netvsc_notify_peers() starts on some other CPU but netdev_notify_peers()
  will hang on rtnl_lock().
- deadlock!

Instead of introducing additional synchronization I suggest we drop
gwrk.dwrk completely and call NETDEV_NOTIFY_PEERS directly. As we're
acting under rtnl lock this is legitimate.

Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Acked-by: Haiyang Zhang <haiyangz@microsoft.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2016-08-15 13:48:07 -07:00
..
2016-07-27 14:03:52 -07:00
2016-08-01 18:36:01 -04:00
2016-08-01 18:36:01 -04:00
2016-07-30 21:01:36 -07:00
2016-07-28 15:45:17 -07:00
2016-08-01 18:36:01 -04:00
2016-08-01 16:49:13 -04:00
2016-07-30 21:01:36 -07:00
2016-08-01 18:36:01 -04:00
2016-08-01 07:25:10 -04:00
2016-07-30 21:01:36 -07:00
2016-07-30 21:01:36 -07:00
2016-08-02 17:05:11 -04:00
2016-08-01 18:36:01 -04:00
2016-07-31 21:36:58 -04:00
2016-08-02 17:05:11 -04:00
2016-07-20 23:39:36 -07:00
2016-07-28 17:38:16 -07:00
2016-07-30 21:01:36 -07:00
2016-07-31 21:36:58 -04:00
2016-07-26 18:27:20 -07:00
2016-08-01 18:36:01 -04:00
2016-08-01 18:36:01 -04:00
2016-08-01 18:36:01 -04:00
2016-08-01 18:37:45 -04:00
2016-08-01 18:36:01 -04:00
2016-08-02 19:35:40 -04:00
2016-07-27 11:35:37 -07:00
2016-07-27 15:18:53 -07:00