]> git.proxmox.com Git - mirror_zfs-debian.git/commit
Fix gcc array subscript above bounds warning
authorNed Bass <bass6@llnl.gov>
Wed, 26 Dec 2012 22:56:41 +0000 (14:56 -0800)
committerBrian Behlendorf <behlendorf1@llnl.gov>
Mon, 7 Jan 2013 19:21:52 +0000 (11:21 -0800)
commit37f000c5aa76613e644cf3e5b1ec7bd2df6f7451
treee78020f4794ff324e6512c03c7a5c3b193349c54
parente44056fcb644496b4dee4847164afe0bb2e04e5b
Fix gcc array subscript above bounds warning

In a debug build, certain GCC versions flag an array bounds warning in
the below code from dnode_sync.c

    } else {
            int i;
            ASSERT(dn->dn_next_nblkptr[txgoff] < dnp->dn_nblkptr);
            /* the blkptrs we are losing better be unallocated */
            for (i = dn->dn_next_nblkptr[txgoff];
                i < dnp->dn_nblkptr; i++)
                    ASSERT(BP_IS_HOLE(&dnp->dn_blkptr[i]));

This usage is in fact safe, since the ASSERT ensures the index does
not exceed to maximum possible number of block pointers. However gcc
can't determine that the assignment 'i = dn->dn_next_nblkptr[txgoff];'
falls within the array bounds so it issues a warning.  To avoid this,
initialize i to zero to make gcc happy but skip the elements before
dn->dn_next_nblkptr[txgoff] in the loop body.  Since a dnode contains
at most 3 block pointers this overhead should be negligible.

Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
Closes #950
module/zfs/dnode_sync.c