summaryrefslogtreecommitdiffstats
path: root/Documentation/fault-injection
diff options
context:
space:
mode:
authorVitaly Kuznetsov <vkuznets@redhat.com>2015-11-27 11:39:55 +0100
committerDavid S. Miller <davem@davemloft.net>2015-12-01 14:58:07 -0500
commit27a70af3f4cf633a1b86c0ac7b426e2fe16ad2e5 (patch)
treee4dc499878da293844034dc90d2894189ae2bda6 /Documentation/fault-injection
parent77b75f4d8cf105b599beef38724f8171e557919d (diff)
downloadlinux-27a70af3f4cf633a1b86c0ac7b426e2fe16ad2e5.tar.gz
linux-27a70af3f4cf633a1b86c0ac7b426e2fe16ad2e5.tar.bz2
linux-27a70af3f4cf633a1b86c0ac7b426e2fe16ad2e5.zip
hv_netvsc: rework link status change handling
There are several issues in hv_netvsc driver with regards to link status change handling: - RNDIS_STATUS_NETWORK_CHANGE results in calling userspace helper doing '/etc/init.d/network restart' and this is inappropriate and broken for many reasons. - link_watch infrastructure only sends one notification per second and in case of e.g. paired disconnect/connect events we get only one notification with last status. This makes it impossible to handle such situations in userspace. Redo link status changes handling in the following way: - Create a list of reconfig events in network device context. - On a reconfig event add it to the list of events and schedule netvsc_link_change(). - In netvsc_link_change() ensure 2-second delay between link status changes. - Handle RNDIS_STATUS_NETWORK_CHANGE as a paired disconnect/connect event. Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'Documentation/fault-injection')
0 files changed, 0 insertions, 0 deletions