The problem #

These two secenairos were described by Colin and Brian in a tech meeing 2008-11-28.

Colin's Scenario#

Brian's Scenario #

Solutions considered#

So far, we have only a brief list (Feel free to flesh these out)

• Judiciously release the lock: may work for Colin's secnario
• require resmgrs to have at least one thread for every mmaped file.
• map the whole file into memory on open: works but inefficeint.
• somehow inform proc that the it's second attempt to lock is for the same purpose of as the existing lock on the aspace
  • pass information though the page fault?
• use multiple finer granularity locks instead of the resmgr lock in the resmgr library

Cultural references quoted #

• we are go for throttle up
• All right, the kernel's secured.
• gaaaame over maaaan