Go to file
Wolfgang Bumiller d21f8a5b5b backup/dynamic_index: explicitly zero-initialize the header
The writer.write_all() call accessed data marked as
undefined to valgrind. Note that we shouldn't write out
uninitialized memory for security reasons anyway.
(note that vec::undefined already did zero-initialize the
data, but also marked it as undefined for valgrind when
compiling with the valgrind feature)

Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2019-08-23 11:42:35 +02:00
debian d/control: depend on libfuse3-dev 2019-08-13 12:29:00 +02:00
docs docs/backup-protocol.rst: add backup protocol docs 2019-06-04 17:33:12 +02:00
etc use service Type=notify 2019-04-25 11:01:33 +00:00
qemu-io add qemu-io crate, AioContext reactor helper 2019-05-16 11:59:55 +02:00
src backup/dynamic_index: explicitly zero-initialize the header 2019-08-23 11:42:35 +02:00
tests disable offensive test 2019-08-21 12:27:50 +02:00
www GUI: fix borders 2019-04-11 12:18:04 +02:00
zstd-sys bump zstd-sys version 2019-06-05 09:44:43 +02:00
.gitignore .gitignore: add local.mak 2019-08-21 10:07:15 +02:00
Cargo.toml remove proxmox-protocol subcrate 2019-08-22 14:08:25 +02:00
defines.mk buildsys: defer some variable expansions 2019-08-21 12:26:10 +02:00
Makefile buildsys: make valgrind=1 to enable valgrind support 2019-05-23 09:49:10 +02:00
rust-toolchain use nightly for now 2019-06-07 13:14:03 +02:00
rustfmt.toml import rustfmt.toml 2019-08-22 13:44:57 +02:00