#2527 BLOC Update.: Rainbow needs to robustly de-allocate resources

[Zarro Boogs per Child]

#2527: Rainbow needs to robustly de-allocate resources
-----------------------+----------------------------------------------------
  Reporter:  mstone    |       Owner:  mstone           
      Type:  defect    |      Status:  new              
  Priority:  blocker   |   Milestone:  Update.1         
 Component:  security  |     Version:                   
Resolution:            |    Keywords:  security, rainbow
  Verified:  0         |  
-----------------------+----------------------------------------------------
Changes (by mstone):

 * cc: marco, tomeu (added)
  * priority:  normal => blocker
  * milestone:  Update.2 => Update.1


Comment:

 We're now using separate namespaces to handle bind-mount cleanup.

 By reserving uids and gids in the range 10000 - 50000 for Rainbow's
 exclusive use, I feel confident that a boot-time deallocation scheme for
 uids will be sufficient to get us from update1 to update2. If anyone is
 concerned that a user might launch 50000 different activity-bundles in the
 span of time from update1 to update2, then I will consider attempting to
 do the book-keeping required to safely deallocate gids.

-- 
Ticket URL: <http://dev.laptop.org/ticket/2527#comment:4>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system