2018 IEEE 23rd Pacific Rim International Symposium on Dependable Computing (PRDC) 2018
DOI: 10.1109/prdc.2018.00035
|View full text |Cite
|
Sign up to set email alerts
|

FastFI: Accelerating Software Fault Injections

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
6
0

Year Published

2020
2020
2024
2024

Publication Types

Select...
7
1

Relationship

1
7

Authors

Journals

citations
Cited by 9 publications
(6 citation statements)
references
References 24 publications
0
6
0
Order By: Relevance
“…Other techniques rely on more lightweight process isolation to avoid the overhead of strong VM isolation. This includes AFEX [4] as well as FastFI [25]. FastFI accelerates SFI experiments through parallelization and by avoiding redundant executions of code that is common to multiple faults and of faulty versions in which the fault location is never reached under a given workload.…”
Section: A Sfi Test Latenciesmentioning
confidence: 99%
See 2 more Smart Citations
“…Other techniques rely on more lightweight process isolation to avoid the overhead of strong VM isolation. This includes AFEX [4] as well as FastFI [25]. FastFI accelerates SFI experiments through parallelization and by avoiding redundant executions of code that is common to multiple faults and of faulty versions in which the fault location is never reached under a given workload.…”
Section: A Sfi Test Latenciesmentioning
confidence: 99%
“…As our approach is conceptually related to that of FastFI [25], we first briefly summarize the FastFI execution model in Sec. III-C1 and discuss why it is not directly applicable to OS kernels.…”
Section: Improving Kernel Epa With Fast Vm Cloningmentioning
confidence: 99%
See 1 more Smart Citation
“…Based on this analysis, they defined a software fault model with 13 fault types, covering 60% of the sample of bugs in the open-source projects [14]. This fault model was used in several other tools, including SAFE [35], HSFI [36], and FastFI [37]. However, these tools focus on a fixed software fault model, with no ability to customize the injected faults according to the specific needs of a project or company.…”
Section: Related Workmentioning
confidence: 99%
“…Unfortunately, fault injection has a high entry barrier, and it is still beyond the reach of the minor service providers, due to the cost and complexity of planning and orchestrate fault injection experiments. Research has been addressing this challenge by developing many solutions applicable both at compile- [15,16] and run-time [17,18]; domain-specific languages to tailor fault injection for the specific system [19,20,21,22]; heuristics aim at minimizing the number of fault injection experiments to identify weak points in the system [23,24,25]; and automated techniques for analyzing fault injection data [26,27]. Despite these advances, it is still difficult to deploy fault injection toolchains into cloud infrastructures.…”
Section: Introductionmentioning
confidence: 99%