summaryrefslogtreecommitdiff
path: root/drivers/clocksource/timer-ti-32k.c
diff options
context:
space:
mode:
authorVitaly Kuznetsov <vkuznets@redhat.com>2016-04-30 19:21:33 -0700
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2018-10-20 09:52:38 +0200
commit43fea648af714b0578f20bfadfec18858e67430d (patch)
tree6577729e68459ee56e06184f3564d82f0c510831 /drivers/clocksource/timer-ti-32k.c
parenteaee7976cf2af79c294ab41d651c0e52488ca868 (diff)
Drivers: hv: kvp: fix IP Failover
commit 4dbfc2e68004c60edab7e8fd26784383dd3ee9bc upstream. Hyper-V VMs can be replicated to another hosts and there is a feature to set different IP for replicas, it is called 'Failover TCP/IP'. When such guest starts Hyper-V host sends it KVP_OP_SET_IP_INFO message as soon as we finish negotiation procedure. The problem is that it can happen (and it actually happens) before userspace daemon connects and we reply with HV_E_FAIL to the message. As there are no repetitions we fail to set the requested IP. Solve the issue by postponing our reply to the negotiation message till userspace daemon is connected. We can't wait too long as there is a host-side timeout (cca. 75 seconds) and if we fail to reply in this time frame the whole KVP service will become inactive. The solution is not ideal - if it takes userspace daemon more than 60 seconds to connect IP Failover will still fail but I don't see a solution with our current separation between kernel and userspace parts. Other two modules (VSS and FCOPY) don't require such delay, leave them untouched. Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com> Signed-off-by: K. Y. Srinivasan <kys@microsoft.com> Signed-off-by: Dexuan Cui <decui@microsoft.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/clocksource/timer-ti-32k.c')
0 files changed, 0 insertions, 0 deletions