Stress-based and path-based fault injection

Tsai, Timothy; Hsueh, Mei-Chen; Zhao, Hongbo; Kalbarczyk, Zbigniew; Iyer, R.K.

doi:10.1109/12.811108

Cited by 50 publications

(25 citation statements)

References 20 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The tool combines a fault injector with a workload generator and monitor, to allow injection of faults under high stress conditions, when faults are more likely to propagate [Tsai et al, 1996[Tsai et al, , 1999. Faults can be injected throughout the system (CPU, memory, disks).…”

Section: Fault Injectionmentioning

confidence: 99%

“…In [Tsai et al, 1999] stress-based injections are performed, where injection is synchronized with high workload activity in the system. Similarly application resource usage is analyzed to guide injection into resources actively used.…”

Section: Related Workmentioning

confidence: 99%

“…In [Tsai et al, 1999] CPU registers and memory are targeted for fault injection using bit-flips. To maximize the activation rate of faults, and their impact, the timing of the injections are controlled by the workload in the system.…”

Section: Event-triggermentioning

confidence: 99%

See 2 more Smart Citations

Robustness Evaluation of Operating Systems

Johansson

2008

Information Assurance

View full text Add to dashboard Cite

SummaryThe premise behind this thesis is the observation that Operating Systems (OS), being the foundation behind operations of computing systems, are complex entities and also subject to failures. Consequently, when they do fail, the impact is the loss of system service and the applications running thereon. While a multitude of sources for OS failures exist, device drivers are often identified as a prominent cause behind failures.In order to characterize the impact of driver failures, at both the OS and application levels, this thesis develops a framework for error propagation-based robustness profiling for an OS. The framework is first developed conceptually and then experimentally validated on a real OS, namely Windows CE .Net. The choice of Windows CE is driven by its representativeness for a multitude of OS's, as well as the ability to customize the OS components for particular needs.For experimental validation, fault injection is a prominent technique that can be used to simulate faults (or errors) in the system by inserting synthetic ones and study their effect. Three key questions with such a technique are where, what and when to inject faults. This thesis shows how injecting errors at the interface between drivers and the OS can be very effective in evaluating the effects driver faults can have.To quantify the OS's robustness, this thesis defines a series of error propagation measures, specifically tailored for device drivers. These measures allow for quantifying and comparing both individual services and device drivers on their susceptibility and diffusing abilities.This thesis compares three contemporary error models on their suitability for robustness evaluation. The classical bit-flip model is found to identify a higher number of severe failures in the system. It also identifies failures for more services than both other models, data type and fuzzing. However, its main drawback is that it requires substantially more injections than the other two. Fuzzing, even though not giving rise to as many failures is able to find new additional services with severe failures.A careful study of the injections performed with the bit-flip model shows that only a few bits are generally useful for identifying new services with robustness weaknesses. Consequently, a new composite model is proposed, combining the most effective bits of the bit-flip model with the fuzzing model's ability to identify new services, giving rise to new model without loss of important information and at the same time incurring a moderate number of injections.To answer the question of when to inject an error this thesis proposes a novel model of a driver's usage profile, focusing on high-level operations being carried out. It guides the injection of errors to instances when the driver is carrying out specific operations. Results from extensive fault injection experiments show that more service vulnerabilities can be discovered. Furthermore, a priori profiling of the drivers can show how effective the proposed approach will be. vi

show abstract

Section: Fault Injectionmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Robustness Evaluation of Operating Systems

Johansson

2008

Information Assurance

View full text Add to dashboard Cite

show abstract

“…Probabilistic approaches, such as those that randomly change values in memory, are limited because they may not trigger particular error handling code [26], while compiler-guided exception raising [12] requires compiler-inserted extra code changing the code under test.…”

Section: Introductionmentioning

confidence: 99%

“…To cover error handling code beyond handling bad user input, researchers have developed fault injection techniques [12,26] that attempt to force the program to execute error handling code. Probabilistic approaches, such as those that randomly change values in memory, are limited because they may not trigger particular error handling code [26], while compiler-guided exception raising [12] requires compiler-inserted extra code changing the code under test.…”

Section: Introductionmentioning

confidence: 99%