Make SecureAllocator a real allocator

XMLWordPrintableJSON

    • Fully Compatible
    • Platforms 13 (04/22/16), Platforms 14 (05/13/16)
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The secure allocator should be more like a real allocator. I.e. it shouldn't require a mmap or virtual alloc call for every allocation.

      We would need to retain the constraints that:

      • Memory is zeroed after deallocate
      • Memory is always locked in memory

      Lets:

      • Always ask the os for full pages of memory
        • hand out multiple allocations from the same page
        • refcount the pages and unlocking and returning after all consumers were gone

              Assignee:
              Mira Carey
              Reporter:
              Mira Carey
              Votes:
              1 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: