zfs/module
Mark Johnston 0c4f86be74 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-22 15:19:08 -07:00
..
avl Links in Source Files 2020-09-03 16:17:18 -07:00
icp ICP: gcm: Allocate hash subkey table separately 2020-10-30 16:06:09 -07:00
lua cppcheck: integrete cppcheck 2021-06-23 13:22:15 -07:00
nvpair Links in Source Files 2020-09-03 16:17:18 -07:00
os file reference counts can get corrupted 2021-09-22 15:19:08 -07:00
spl Cleanup linux module kbuild files 2020-06-10 09:24:15 -07:00
unicode Throw const on some strings 2020-10-16 12:55:56 -07:00
zcommon Fix AVX512BW Fletcher code on AVX512-but-not-BW machines 2021-06-23 13:22:14 -07:00
zfs Initialize dn_next_type[] in the dnode constructor 2021-09-22 15:19:08 -07:00
zstd Optimize locking checks in mempool allocator 2020-11-03 09:51:10 -08: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-03-05 12:50:32 -08:00
Makefile.in cppcheck: integrete cppcheck 2021-06-23 13:22:15 -07:00