Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-19929

Audit sharding code for potential use-after-frees

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Done
    • Affects Version/s: 3.1.6
    • Fix Version/s: None
    • Component/s: Sharding
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Sharding 9 (09/18/15), Sharding A (10/09/15)
    • Linked BF Score:
      0

      Description

      There have been at least 3 crashes in sharding code caused by use-after-frees or the misuse of references in the 3.1.x cycle: SERVER-19367, SERVER-19839, and SERVER-18815 (the last commit)

      We should proactively search for similar issues to avoid costly debugging later.

        Attachments

          Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-19367 Segfault establishing shard connection in Chunk::splitMulti

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-19839 Use-after-free in ShardRegistry::runCommandWithNotMasterRetries

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-18815 Shard object lifetime shoud be managed by the ShardRegistry

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-20559 Race condition in shard registry during concurrent sharding operations

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-20629 Use-after-free in CatalogManagerReplicaSet::_runReadCommand

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: