Move range_tree, btree, highbit64 to common code

Break out the range_tree, btree, and highbit64/lowbit64 code from kernel
space into shared kernel and userspace code.  This is needed for the
updated `zpool status -vv` error byte range reporting that will be
coming in a future commit.  That commit needs the range_tree code in
kernel and userspace.

Reviewed-by: Rob Norris <robn@despairlabs.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: Tony Hutter <hutter2@llnl.gov>
Closes #18133
This commit is contained in:
Tony Hutter
2026-02-22 11:43:51 -08:00
committed by GitHub
parent 168023b603
commit d2f5cb3a50
15 changed files with 117 additions and 88 deletions
+9
View File
@@ -59,6 +59,15 @@ nodist_libzfs_la_SOURCES = \
module/zcommon/zpool_prop.c \
module/zcommon/zprop_common.c
# Special case:
#
# We need to include btree.c and range_tree.c as SOURCES rather than
# LIBADD'ing them. This is because LIBADD'ing them will add their symbols to
# the libzfs API, which we do not want at this time.
nodist_libzfs_la_SOURCES += \
module/zfs/btree.c \
module/zfs/range_tree.c
libzfs_la_LIBADD = \
libzfs_core.la \
libnvpair.la \