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

Init-order fiasco in secure_allocator

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 6.0.0-rc0
    • None
    • None
    • None
    • Fully Compatible
    • ALL
    • Service Arch 2022-03-21
    • 167
    • 1

    Description

      Init-order fiasco in secure_allocator.

      It accesses a namespace scope hash table to construct namespace scope objects.

      These are the newly changed:

      FLEIndexKey indexKey(KeyMaterial(indexVec.begin(), indexVec.end()));
      

      in this case (SERVER-63645). It is just a symptom though.

      This is not going to work unless the link order accidentally makes it work.

      https://evergreen.mongodb.com/task/mongodb_mongo_master_ubuntu1804_debug_aubsan_lite_required_run_unittests_c0652d91db0fb5cc54f12811e100ec8108130112_22_03_10_19_19_03

      Affecting ASAN in mongodb-mongo-master waterfall.

      The secure allocator has to be ALWAYS available, including for the initialization of global static duration objects and must be alive during their destruction.

      Hide all such instances behind local static immortals.

      Attachments

        Activity

          People

            billy.donahue@mongodb.com Billy Donahue
            billy.donahue@mongodb.com Billy Donahue
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: