From 6d8da84106de1fc8480e1758cc88e81393b4c0c2 Mon Sep 17 00:00:00 2001 From: Matthew Macy Date: Sat, 25 Jul 2020 20:07:44 -0700 Subject: Make use of ZFS_DEBUG consistent within kmod sources Reviewed-by: Brian Behlendorf Reviewed-by: Ryan Moeller Signed-off-by: Matt Macy Closes #10623 --- module/zfs/space_map.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'module/zfs/space_map.c') diff --git a/module/zfs/space_map.c b/module/zfs/space_map.c index 25da0e63c..723fa0578 100644 --- a/module/zfs/space_map.c +++ b/module/zfs/space_map.c @@ -675,7 +675,7 @@ space_map_write_impl(space_map_t *sm, range_tree_t *rt, maptype_t maptype, space_map_write_intro_debug(sm, maptype, tx); -#ifdef DEBUG +#ifdef ZFS_DEBUG /* * We do this right after we write the intro debug entry * because the estimate does not take it into account. @@ -736,7 +736,7 @@ space_map_write_impl(space_map_t *sm, range_tree_t *rt, maptype_t maptype, dmu_buf_rele(db, FTAG); -#ifdef DEBUG +#ifdef ZFS_DEBUG /* * We expect our estimation to be based on the worst case * scenario [see comment in space_map_estimate_optimal_size()]. -- cgit v1.2.3