Mark Johnston ac573e3105 Initialize dn_next_type[] in the dnode constructor ... It seems nothing ensures that this array is zeroed when a dnode is freshly allocated, so in principle it retains the values from the previous allocation. In practice it seems to be the case that the fields should end up zeroed, but we can zero the field anyway for consistency. 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 13:07:44 -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	Initialize dn_next_type[] in the dnode constructor	2021-09-14 13:07:44 -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