DAMON code has a few assumptions that can be critical if violated. Validating the assumptions in code can be useful at finding such critical bugs. I was actually adding some such additional sanity checks in my personal tree, and those were useful at finding bugs that I made during the development of new patches. We also found [1] sometimes the assumptions are misunderstood. The validation can work as good documentation for such cases.
Add some of such debugging purpose sanity checks. Because those additional checks can impose more overhead, make those only optional via new config, CONFIG_DAMON_DEBUG_SANITY, that is recommended for only development and test setups. And as recommended, enable it for DAMON kunit tests and selftests. [1] https://lore.kernel.org/[email protected] SeongJae Park (10): mm/damon: add CONFIG_DAMON_DEBUG_SANITY mm/damon/core: add damon_new_region() debug_sanity check mm/damon/core: add damon_del_region() debug_sanity check mm/damon/core: add damon_nr_regions() debug_sanity check mm/damon/core: add damon_merge_two_regions() debug_sanity check mm/damon/core: add damon_merge_regions_of() debug_sanity check mm/damon/core: add damon_split_region_at() debug_sanity check mm/damon/core: add damon_reset_aggregated() debug_sanity check mm/damon/tests/.kunitconifg: enable DAMON_DEBUG_SANITY tools/testing/selftests/damon/config: enable DAMON_DEBUG_SANITY mm/damon/Kconfig | 11 +++ mm/damon/core.c | 139 +++++++++++++++++++++++++++ mm/damon/tests/.kunitconfig | 3 + tools/testing/selftests/damon/config | 1 + 4 files changed, 154 insertions(+) base-commit: e059221c54896e36c8fc320029648e9013b382ea -- 2.47.3
