Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-11719

Refactor search_itree

Details

    • 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

          is related to

          Bug - A problem which impairs or prevents the functions of the product. LU-13908 ldlm_lock_put()) ASSERTION( (((( lock))->l_flags & (1ULL << 50)) != 0) ) failed

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved
          is related to

          Bug - A problem which impairs or prevents the functions of the product. LU-11670 Incorrect size when using lockahead

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved

          Activity

            People

              paf Patrick Farrell (Inactive)
              paf Patrick Farrell (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: