diff options
author | Fabiano Rosas <farosas@suse.de> | 2024-12-09 17:44:23 -0300 |
---|---|---|
committer | Fabiano Rosas <farosas@suse.de> | 2025-01-02 16:00:50 -0300 |
commit | 117221ad999a3d027d38ae9ddbaa94d4e1d6a303 (patch) | |
tree | db6f928b756632d62abd11d03c337bd21e3a113f | |
parent | cd196679f413c7905143e5eb9b7d63b7a7eea158 (diff) | |
download | qemu-117221ad999a3d027d38ae9ddbaa94d4e1d6a303.zip qemu-117221ad999a3d027d38ae9ddbaa94d4e1d6a303.tar.gz qemu-117221ad999a3d027d38ae9ddbaa94d4e1d6a303.tar.bz2 |
tests/qtest/migration: Initialize buffer in probe_o_direct_support
Valgrind complains about the probe_o_direct_support() function reading
from an uninitialized buffer. For probing O_DIRECT support we don't
actually need to write to the file, just make sure the pwrite call
doesn't reject the write. Still, write zeroes to the buffer to
suppress the warning.
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Reviewed-by: Peter Xu <peterx@redhat.com>
Message-Id: <20241209204427.17763-3-farosas@suse.de>
Signed-off-by: Fabiano Rosas <farosas@suse.de>
-rw-r--r-- | tests/qtest/migration/migration-util.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/tests/qtest/migration/migration-util.c b/tests/qtest/migration/migration-util.c index 525bf1e..401fe27 100644 --- a/tests/qtest/migration/migration-util.c +++ b/tests/qtest/migration/migration-util.c @@ -284,6 +284,7 @@ bool probe_o_direct_support(const char *tmpfs) buf = qemu_try_memalign(len, len); g_assert(buf); + memset(buf, 0, len); ret = pwrite(fd, buf, len, offset); unlink(filename); |