[src/trunk]: src/external/cddl/osnet/dist/uts/common/fs/zfs i can't confirm o...

[mrg <mrg%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/f4e3fa100977
branches:  trunk
changeset: 943650:f4e3fa100977
user:      mrg <mrg%NetBSD.org@localhost>
date:      Mon Sep 07 07:44:53 2020 +0000

description:
i can't confirm or deny that GCC 9 is wrong about parity_valid[]
having uninitialised members, but since setting up reconstruct
isn't a hot path, just zero init the whole thing to be sure.

diffstat:

 external/cddl/osnet/dist/uts/common/fs/zfs/vdev_raidz.c |  2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diffs (12 lines):

diff -r 41f9bb4daccb -r f4e3fa100977 external/cddl/osnet/dist/uts/common/fs/zfs/vdev_raidz.c
--- a/external/cddl/osnet/dist/uts/common/fs/zfs/vdev_raidz.c   Mon Sep 07 07:43:36 2020 +0000
+++ b/external/cddl/osnet/dist/uts/common/fs/zfs/vdev_raidz.c   Mon Sep 07 07:44:53 2020 +0000
@@ -1412,7 +1412,7 @@
        int i, c;
        int code;
        int nbadparity, nbaddata;
-       int parity_valid[VDEV_RAIDZ_MAXPARITY];
+       int parity_valid[VDEV_RAIDZ_MAXPARITY] = {0};
 
        /*
         * The tgts list must already be sorted.