Efficient software-based fault isolation
Robert Wahbe, Steven E. Lucco, Thomas E. Anderson et al. · ACM SIGOPS Operating Systems Review · 1993
One way to provide fault isolation among cooperating software modules is to place each in its own address space. However, for tightly-coupled modules, this solution incurs prohibitive context switch overhead. In this paper, we present a software approach to implementing fault isolation within a single address space.Our approach has two parts. First, we load the code and data for a distrusted module into its own fault do main , a logically separate portion of the application's address space. Second, we modify the object code of a distrusted module to prevent it from writing or jumping to an address outside its fault domain. Both these software operations are portable and programming language independent.Our approach poses a tradeoff relative to hardware fault isolation: substantially faster communication between fault domains, at a cost of slightly increased execution time for distrusted modules. We demonstrate that for frequently communicating modules, implementing fault isolation in software rather than hardware can substantially improve end-to-end application performance.
Cited by 251 works. doi:10.1145/173668.168635
Authors
References
- Scale and performance in a distributed file system
- Implementing remote procedure calls
- The BSD packet filter: a new architecture for user-level packet capture
- Active messages
- Pilot
- The SEQUOIA 2000 storage benchmark
- Vnodes: An Architecture for Multiple File System Types in Sun UNIX.
- A comparison of list schedules for parallel processing systems
- Lightweight remote procedure call
- Binary translation