Mark Johnston 99df200ffc Zero pad bytes following TX_WRITE log data ... When logging a TX_WRITE record in the case where file data has to be copied from the DMU, we pad the log record size to a multiple of 8 bytes. In this case, any padding bytes should be zeroed, otherwise the contents of uninitialized memory are written to the ZIL. This was found using KMSAN. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: Alexander Motin <mav@FreeBSD.org> Signed-off-by: Mark Johnston <markj@FreeBSD.org> Closes #12383		2021-09-14 12:42:21 -07:00
..
avl	Fix various typos	2021-04-07 13:27:11 -07:00
icp	Replace ZoL with OpenZFS where applicable	2021-05-10 12:16:46 -07:00
lua	cppcheck: integrete cppcheck	2021-01-26 16:12:26 -08:00
nvpair	A few fixes of callback typecasting (for the upcoming ClangCFI)	2021-09-14 12:39:48 -07:00
os	Linux 5.14 compat: explicity assign set_page_dirty	2021-09-14 12:41:10 -07:00
spl	Cleanup linux module kbuild files	2020-06-10 09:24:15 -07:00
unicode	Fix various typos	2021-04-07 13:27:11 -07:00
zcommon	Fix AVX512BW Fletcher code on AVX512-but-not-BW machines	2021-05-10 12:05:36 -07:00
zfs	Zero pad bytes following TX_WRITE log data	2021-09-14 12:42:21 -07:00
zstd	Fix build with KASAN	2021-06-29 13:14:42 -07:00
.gitignore	Cleanup linux module kbuild files	2020-06-10 09:24:15 -07:00
Kbuild.in	Add zstd support to zfs	2020-08-20 10:30:06 -07:00
Makefile.bsd	Restore FreeBSD resource usage accounting	2021-02-19 22:34:33 -08:00
Makefile.in	FreeBSD module --enable-debug --enable-invariants	2021-03-05 12:16:41 -08:00