Somewhere between v6 and v7 the of the zero-copy-send patchset a crucial part of the flushing mechanism got missing: incrementing zero_copy_queued.
Without that, the flushing interface becomes a no-op, and there is no guarantee the buffer is really sent. This can go as bad as causing a corruption in RAM during migration. Fixes: 2bc58ffc2926 ("QIOChannelSocket: Implement io_writev zero copy flag & io_flush for CONFIG_LINUX") Reported-by: 徐闯 <xuchuangxc...@bytedance.com> Signed-off-by: Leonardo Bras <leob...@redhat.com> --- io/channel-socket.c | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/io/channel-socket.c b/io/channel-socket.c index ef7c7cfbac..ca4cae930f 100644 --- a/io/channel-socket.c +++ b/io/channel-socket.c @@ -607,6 +607,11 @@ static ssize_t qio_channel_socket_writev(QIOChannel *ioc, "Unable to write to socket"); return -1; } + + if (zero_copy_enabled) { + sioc->zero_copy_queued++; + } + return ret; } #else /* WIN32 */ -- 2.36.1