android_kernel_xiaomi_sm7250/drivers/hv
Dexuan Cui 0a3172f9c5 Drivers: hv: vmbus: Ignore CHANNELMSG_TL_CONNECT_RESULT(23)
[ Upstream commit ddc9d357b991838c2d975e8d7e4e9db26f37a7ff ]

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>
2020-08-11 15:32:33 +02:00
..
channel_mgmt.c Drivers: hv: vmbus: Ignore CHANNELMSG_TL_CONNECT_RESULT(23) 2020-08-11 15:32:33 +02:00
channel.c vmbus: keep pointer to ring buffer page 2019-11-20 18:47:31 +01:00
connection.c
hv_balloon.c hv_balloon: Balloon up according to request page number 2020-02-11 04:34:01 -08:00
hv_fcopy.c
hv_kvp.c
hv_snapshot.c
hv_trace_balloon.h
hv_trace.c
hv_trace.h
hv_util.c
hv_utils_transport.c
hv_utils_transport.h
hv.c
hyperv_vmbus.h
Kconfig
Makefile
ring_buffer.c
vmbus_drv.c Drivers: hv: vmbus: Ignore CHANNELMSG_TL_CONNECT_RESULT(23) 2020-08-11 15:32:33 +02:00