Details
-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
3
-
9223372036854775807
Description
The behavior of search_itree is different from its close relative search_queue in ways that are a little confusing. Also, in some cases, it will continue searching the trees after a lock has been found.
This is a low priority bug to slightly refactor its behavior, inspired because the difference between search_itree and search_queue introduced a subtle bug in the LU-11670 patch.