> Would it make sense to include > valgrind/memcheck.h and use VALGRIND_MAKE_MEM_DEFINED? We already include the header and use VALGRIND_MAKE_MEM_DEFINED in many places in libibverbs. However in this case I think we really should be zeroing out reserved fields in the data we pass to the kernel.