Rolf Neugebauer aa885f3bb3 kernel: update kernel patches ...

On older Windows builds (e.g. 10586) the 4.9.x TimeSync integration
service spams the logs with multiple messages a second of the form:
hv_utils: Using TimeSync version 4.0

It seems that a new protocol version was introduced with newer
Windows 10 builds but the kernel patches don't negotiate the
protocol version based on what the host supports, but instead
simply use the Windows version of the host.

Added two new patches:
- the first one is a cherry-pick from upstream which fixes some
  of the TimeSync protocol negotiation, but does not fix the issue.
- the second one forces the TimeSync protocol to version 3.0 even on
  Windows 10 hosts.

Patches based on: https://github.com/rneugeba/linux-stable/tree/v4.9.2-moby

Signed-off-by: Rolf Neugebauer <rolf.neugebauer@docker.com>

2017-01-12 00:14:23 +00:00

..

0001-VSOCK-Only-allow-host-network-namespace-to-use-AF_VS.patch

kernel: update kernel patches

2017-01-12 00:14:23 +00:00

0002-hv_sock-introduce-Hyper-V-Sockets.patch

kernel: update kernel patches

2017-01-12 00:14:23 +00:00

0003-vmbus-Don-t-spam-the-logs-with-unknown-GUIDs.patch

kernel: update kernel patches

2017-01-12 00:14:23 +00:00

0004-Drivers-hv-utils-Fix-the-mapping-between-host-versio.patch

kernel: update kernel patches

2017-01-12 00:14:23 +00:00

0005-Drivers-hv-utils-Force-TimeSync-version-3.0-on-Windo.patch

kernel: update kernel patches

2017-01-12 00:14:23 +00:00