diff options
| author | Mark Johnston <[email protected]> | 2021-07-16 10:12:47 -0400 |
|---|---|---|
| committer | Tony Hutter <[email protected]> | 2021-09-14 13:07:44 -0700 |
| commit | ac573e31053ff4052fb74a0891ba6deae44f497c (patch) | |
| tree | 46670ea88e278d0a8642232fdcc3d2460ee3e8ea /tests/runfiles | |
| parent | 99df200ffce8a100146861295d9b1a41a5ff9104 (diff) | |
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 <[email protected]>
Reviewed-by: Alexander Motin <[email protected]>
Signed-off-by: Mark Johnston <[email protected]>
Closes #12383
Diffstat (limited to 'tests/runfiles')
0 files changed, 0 insertions, 0 deletions