diff options
| author |   Dexuan Cui <decui@microsoft.com> | 2020-01-19 15:29:22 -0800 |
|---|---|---|
| committer |   Sasha Levin <sashal@kernel.org> | 2020-01-25 16:52:11 -0500 |
| commit | ddc9d357b991838c2d975e8d7e4e9db26f37a7ff (patch) | |
| tree | 48369ba9e87a07244c6f8f1d1b6061be6fc20668 /include/linux/hyperv.h | |
| parent | video: hyperv_fb: Fix hibernation for the deferred IO feature (diff) | |
| download | wireguard-linux-ddc9d357b991838c2d975e8d7e4e9db26f37a7ff.tar.xz wireguard-linux-ddc9d357b991838c2d975e8d7e4e9db26f37a7ff.zip | |
Drivers: hv: vmbus: Ignore CHANNELMSG_TL_CONNECT_RESULT(23)
When a Linux hv_sock app tries to connect to a Service GUID on which no
host app is listening, a recent host (RS3+) sends a
CHANNELMSG_TL_CONNECT_RESULT (23) message to Linux and this triggers such
a warning:
unknown msgtype=23
WARNING: CPU: 2 PID: 0 at drivers/hv/vmbus_drv.c:1031 vmbus_on_msg_dpc
Actually Linux can safely ignore the message because the Linux app's
connect() will time out in 2 seconds: see VSOCK_DEFAULT_CONNECT_TIMEOUT
and vsock_stream_connect(). We don't bother to make use of the message
because: 1) it's only supported on recent hosts; 2) a non-trivial effort
is required to use the message in Linux, but the benefit is small.
So, let's not see the warning by silently ignoring the message.
Signed-off-by: Dexuan Cui <decui@microsoft.com>
Reviewed-by: Michael Kelley <mikelley@microsoft.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'include/linux/hyperv.h')
| -rw-r--r-- | include/linux/hyperv.h | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/include/linux/hyperv.h b/include/linux/hyperv.h index 26f3aeeae1ca..41c58011431e 100644 --- a/include/linux/hyperv.h +++ b/include/linux/hyperv.h @@ -425,6 +425,8 @@ enum vmbus_channel_message_type { CHANNELMSG_19 = 19, CHANNELMSG_20 = 20, CHANNELMSG_TL_CONNECT_REQUEST = 21, + CHANNELMSG_22 = 22, + CHANNELMSG_TL_CONNECT_RESULT = 23, CHANNELMSG_COUNT }; |