Lines Matching defs:checksum
931 void *data, int checksum, zio_done_func_t *done, void *private,
945 zio->io_prop.zp_checksum = checksum;
952 void *data, int checksum, zio_done_func_t *done, void *private,
966 zio->io_prop.zp_checksum = checksum;
968 if (zio_checksum_table[checksum].ci_flags & ZCHECKSUM_FLAG_EMBEDDED) {
971 * the end of the write buffer to hold the verifier/checksum.
1000 * checksum and the parent need not. This pushes error
1769 * as the verifier to ensure uniqueness of the SHA256 checksum.
1770 * Critically, the gang block bp's blk_cksum is the checksum of the data,
1840 * a new gang block header checksum for it; but no one will
1841 * compute a new data checksum, so we do that here. The one
1843 * its data checksum because that stage precedes gang assembly.
2207 * By leveraging a cryptographically secure checksum, such as SHA256, we
2215 * That said, there are no known attacks against the checksum algorithms
2235 * characteristics (i.e. same checksum, compression algorithms, etc).
2554 * If we're using a weak checksum, upgrade to a strong checksum
2555 * and try again. If we're already using a strong checksum,
3085 * disk, and use that to finish the checksum ereport later.
3223 enum zio_checksum checksum;
3228 * We're either generating a label checksum, or none at all.
3230 checksum = zio->io_prop.zp_checksum;
3232 if (checksum == ZIO_CHECKSUM_OFF)
3235 ASSERT(checksum == ZIO_CHECKSUM_LABEL);
3239 checksum = ZIO_CHECKSUM_GANG_HEADER;
3241 checksum = BP_GET_CHECKSUM(bp);
3245 zio_checksum_compute(zio, checksum, zio->io_data, zio->io_size);
3262 * We're either verifying a label checksum, or nothing at all.
3284 * Called by RAID-Z to ensure we don't compute the checksum twice.
3532 * checksum reports now while we still have the transformed data.
3717 * Report any checksum errors, since the I/O is complete.