Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-1921

If next_random lands on a deleted item, don't search

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: WT2.6.0
    • Labels:
      None
    • # Replies:
      1
    • Last comment by Customer:
      true

      Description

      After review of the next_random implementation, we are concerned that it could read from an invalid pointer if the initial random walk lands on a deleted item.

        Issue Links

          Activity

          • Comments
          Hide
          xgen-internal-githook Githook User added a comment -

          Author:

          {u'username': u'michaelcahill', u'name': u'Michael Cahill', u'email': u'michael.cahill@mongodb.com'}

          Message: If a random lookup lands on a deleted item, move to the next valid record (or the last record in the table if there is no valid record after the search point). This avoids a call to search_near when there may be no key set.

          refs WT-1921
          Branch: develop
          https://github.com/wiredtiger/wiredtiger/commit/c139dd0d1c63b4e6a307367d34bf75fe675d9016

          Show
          xgen-internal-githook Githook User added a comment - Author: {u'username': u'michaelcahill', u'name': u'Michael Cahill', u'email': u'michael.cahill@mongodb.com'} Message: If a random lookup lands on a deleted item, move to the next valid record (or the last record in the table if there is no valid record after the search point). This avoids a call to search_near when there may be no key set. refs WT-1921 Branch: develop https://github.com/wiredtiger/wiredtiger/commit/c139dd0d1c63b4e6a307367d34bf75fe675d9016

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Days since reply:
                1 year, 46 weeks ago
                Date of 1st Reply: