| commit | 3ee9a997a34dea4f9b509ac3e45085929b068008 | |
| author | Mark Johnston <markjdb@gmail.com> | |
| Mon, 23 Aug 2021 18:10:17 +0000 (23 14:10 -0400) | ||
| committer | GitHub <noreply@github.com> | |
| Mon, 23 Aug 2021 18:10:17 +0000 (23 11:10 -0700) | ||
| tree | d6d1c13105f1d161e1d2362051415b1c29e3ff0b | treesnapshot (tar.gz zip) |
| parent | 8ae86e2edc736483c1530fd689525aa2460eaec8 | commitdiff |
Initialize parity blocks before RAID-Z reconstruction benchmarking
benchmark_raidz() allocates a row to benchmark parity calculation and
reconstruction. In the latter case, the parity blocks are left
uninitialized, leading to reports from KMSAN.
Initialize parity blocks to 0xAA as we do for the data earlier in the
function. This does not affect the selected RAID-Z implementation on
any of several systems tested.
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: Mark Johnston <markj@FreeBSD.org>
Closes #12473
benchmark_raidz() allocates a row to benchmark parity calculation and
reconstruction. In the latter case, the parity blocks are left
uninitialized, leading to reports from KMSAN.
Initialize parity blocks to 0xAA as we do for the data earlier in the
function. This does not affect the selected RAID-Z implementation on
any of several systems tested.
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: Mark Johnston <markj@FreeBSD.org>
Closes #12473
| module/zfs/vdev_raidz_math.c | diffblobblamehistory |