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.
Attachments
Issue Links
Activity
Fix Version/s | New: Lustre 2.12.6 [ 14707 ] |
Link | New: This issue is related to ANL-4 [ ANL-4 ] |
Link | New: This issue is related to DDN-1669 [ DDN-1669 ] |
Link | New: This issue is related to DDN-1636 [ DDN-1636 ] |
Link | New: This issue is duplicated by BULL-50 [ BULL-50 ] |
Link | New: This issue is related to EDU-158 [ EDU-158 ] |
Fix Version/s | New: Lustre 2.13.0 [ 14290 ] | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Labels | New: patch |