Hi, After upgrading our VMs kernel, our golang software stack started facing some communication stalling on HyperV platforms. After receiving a few hundered MBs data from a vsocket in the guest, the data flows suddenly stops, and the receiver is not notified. The sender on the host times out. Since the use case is very simple, we were surprised that it was not reported, so we took time to investigate. The issue was bisected to patch below [b3f7fd54881bcba5dc529935f38] af_vsock: separate wait data loop >From there ftrace allowed to spot the problem, more details are in the patch description. In the end, note that the patch is not HyperV specific. So maybe the reproduction rate is lower on other platforms. Let me know what you think, Frédéric Dalleau Frédéric Dalleau (1): vsock: Fix stalled communication on vhost sockets net/vmw_vsock/af_vsock.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) -- 2.34.1 _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/virtualization
