Do injected faults cause real failures? A case study of linux

Nobuo Kikuchi, Takeshi Yoshimura, Ryo Sakuma, Kenji Kono

Research output: Chapter in Book/Report/Conference proceedingConference contribution

2 Citations (Scopus)

Abstract

Software fault injection (SFI) has been used to intentionally cause 'failures' in software components and assess their impacts on the entire software system. A key property that SFI should satisfy is the representative ness of injected failures, the failures caused by SFI should be as close as possible to failures in the wild. If injected failures do not represent realistic failures, the measured resilience or tolerance against failures of the investigated system is not trustworthy. To the best of the authors' knowledge, the representative ness of 'faults' has been investigated. However, it is an open problem whether the failures caused by injected faults represent realistic failures. In this paper, we report the preliminary results of the investigation on the representative ness of injected failures. To compare injected failures with real failures, we have collected 43,742 real crash logs of Linux from the Red Hat repository, and conducted a fault injection campaign on Linux, using SAFE, a state-of-theatre injector of software faults. In the fault injection campaign, 50,000 faults are injected to the Linux file system and 71,470 runs of a workload are executed. The crash logs generated by SFI are compared with the real Red Hat logs with respect to crash causes, crashed system calls, and crashed modules. Our preliminary results suggest that failures caused by injected faults do not represent real failures, probably because injected faults are not representative enough or because the selected workload is not realistic.

Original languageEnglish
Title of host publicationProceedings - IEEE 25th International Symposium on Software Reliability Engineering Workshops, ISSREW 2014
PublisherInstitute of Electrical and Electronics Engineers Inc.
Pages174-179
Number of pages6
ISBN (Print)9781479973774
DOIs
Publication statusPublished - 2014 Dec 12
Event25th IEEE International Symposium on Software Reliability Engineering Workshops, ISSREW 2014 - Naples, Italy
Duration: 2014 Nov 32014 Nov 6

Other

Other25th IEEE International Symposium on Software Reliability Engineering Workshops, ISSREW 2014
CountryItaly
CityNaples
Period14/11/314/11/6

Fingerprint

Theaters
Linux

Keywords

  • Failure analysis
  • Operating systems
  • Software fault injection

ASJC Scopus subject areas

  • Software
  • Safety, Risk, Reliability and Quality

Cite this

Kikuchi, N., Yoshimura, T., Sakuma, R., & Kono, K. (2014). Do injected faults cause real failures? A case study of linux. In Proceedings - IEEE 25th International Symposium on Software Reliability Engineering Workshops, ISSREW 2014 (pp. 174-179). [6983834] Institute of Electrical and Electronics Engineers Inc.. https://doi.org/10.1109/ISSREW.2014.104

Do injected faults cause real failures? A case study of linux. / Kikuchi, Nobuo; Yoshimura, Takeshi; Sakuma, Ryo; Kono, Kenji.

Proceedings - IEEE 25th International Symposium on Software Reliability Engineering Workshops, ISSREW 2014. Institute of Electrical and Electronics Engineers Inc., 2014. p. 174-179 6983834.

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Kikuchi, N, Yoshimura, T, Sakuma, R & Kono, K 2014, Do injected faults cause real failures? A case study of linux. in Proceedings - IEEE 25th International Symposium on Software Reliability Engineering Workshops, ISSREW 2014., 6983834, Institute of Electrical and Electronics Engineers Inc., pp. 174-179, 25th IEEE International Symposium on Software Reliability Engineering Workshops, ISSREW 2014, Naples, Italy, 14/11/3. https://doi.org/10.1109/ISSREW.2014.104
Kikuchi N, Yoshimura T, Sakuma R, Kono K. Do injected faults cause real failures? A case study of linux. In Proceedings - IEEE 25th International Symposium on Software Reliability Engineering Workshops, ISSREW 2014. Institute of Electrical and Electronics Engineers Inc. 2014. p. 174-179. 6983834 https://doi.org/10.1109/ISSREW.2014.104
Kikuchi, Nobuo ; Yoshimura, Takeshi ; Sakuma, Ryo ; Kono, Kenji. / Do injected faults cause real failures? A case study of linux. Proceedings - IEEE 25th International Symposium on Software Reliability Engineering Workshops, ISSREW 2014. Institute of Electrical and Electronics Engineers Inc., 2014. pp. 174-179
@inproceedings{331161c0f6814b669b3b1322d29b12bf,
title = "Do injected faults cause real failures? A case study of linux",
abstract = "Software fault injection (SFI) has been used to intentionally cause 'failures' in software components and assess their impacts on the entire software system. A key property that SFI should satisfy is the representative ness of injected failures, the failures caused by SFI should be as close as possible to failures in the wild. If injected failures do not represent realistic failures, the measured resilience or tolerance against failures of the investigated system is not trustworthy. To the best of the authors' knowledge, the representative ness of 'faults' has been investigated. However, it is an open problem whether the failures caused by injected faults represent realistic failures. In this paper, we report the preliminary results of the investigation on the representative ness of injected failures. To compare injected failures with real failures, we have collected 43,742 real crash logs of Linux from the Red Hat repository, and conducted a fault injection campaign on Linux, using SAFE, a state-of-theatre injector of software faults. In the fault injection campaign, 50,000 faults are injected to the Linux file system and 71,470 runs of a workload are executed. The crash logs generated by SFI are compared with the real Red Hat logs with respect to crash causes, crashed system calls, and crashed modules. Our preliminary results suggest that failures caused by injected faults do not represent real failures, probably because injected faults are not representative enough or because the selected workload is not realistic.",
keywords = "Failure analysis, Operating systems, Software fault injection",
author = "Nobuo Kikuchi and Takeshi Yoshimura and Ryo Sakuma and Kenji Kono",
year = "2014",
month = "12",
day = "12",
doi = "10.1109/ISSREW.2014.104",
language = "English",
isbn = "9781479973774",
pages = "174--179",
booktitle = "Proceedings - IEEE 25th International Symposium on Software Reliability Engineering Workshops, ISSREW 2014",
publisher = "Institute of Electrical and Electronics Engineers Inc.",

}

TY - GEN

T1 - Do injected faults cause real failures? A case study of linux

AU - Kikuchi, Nobuo

AU - Yoshimura, Takeshi

AU - Sakuma, Ryo

AU - Kono, Kenji

PY - 2014/12/12

Y1 - 2014/12/12

N2 - Software fault injection (SFI) has been used to intentionally cause 'failures' in software components and assess their impacts on the entire software system. A key property that SFI should satisfy is the representative ness of injected failures, the failures caused by SFI should be as close as possible to failures in the wild. If injected failures do not represent realistic failures, the measured resilience or tolerance against failures of the investigated system is not trustworthy. To the best of the authors' knowledge, the representative ness of 'faults' has been investigated. However, it is an open problem whether the failures caused by injected faults represent realistic failures. In this paper, we report the preliminary results of the investigation on the representative ness of injected failures. To compare injected failures with real failures, we have collected 43,742 real crash logs of Linux from the Red Hat repository, and conducted a fault injection campaign on Linux, using SAFE, a state-of-theatre injector of software faults. In the fault injection campaign, 50,000 faults are injected to the Linux file system and 71,470 runs of a workload are executed. The crash logs generated by SFI are compared with the real Red Hat logs with respect to crash causes, crashed system calls, and crashed modules. Our preliminary results suggest that failures caused by injected faults do not represent real failures, probably because injected faults are not representative enough or because the selected workload is not realistic.

AB - Software fault injection (SFI) has been used to intentionally cause 'failures' in software components and assess their impacts on the entire software system. A key property that SFI should satisfy is the representative ness of injected failures, the failures caused by SFI should be as close as possible to failures in the wild. If injected failures do not represent realistic failures, the measured resilience or tolerance against failures of the investigated system is not trustworthy. To the best of the authors' knowledge, the representative ness of 'faults' has been investigated. However, it is an open problem whether the failures caused by injected faults represent realistic failures. In this paper, we report the preliminary results of the investigation on the representative ness of injected failures. To compare injected failures with real failures, we have collected 43,742 real crash logs of Linux from the Red Hat repository, and conducted a fault injection campaign on Linux, using SAFE, a state-of-theatre injector of software faults. In the fault injection campaign, 50,000 faults are injected to the Linux file system and 71,470 runs of a workload are executed. The crash logs generated by SFI are compared with the real Red Hat logs with respect to crash causes, crashed system calls, and crashed modules. Our preliminary results suggest that failures caused by injected faults do not represent real failures, probably because injected faults are not representative enough or because the selected workload is not realistic.

KW - Failure analysis

KW - Operating systems

KW - Software fault injection

UR - http://www.scopus.com/inward/record.url?scp=84922679174&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=84922679174&partnerID=8YFLogxK

U2 - 10.1109/ISSREW.2014.104

DO - 10.1109/ISSREW.2014.104

M3 - Conference contribution

SN - 9781479973774

SP - 174

EP - 179

BT - Proceedings - IEEE 25th International Symposium on Software Reliability Engineering Workshops, ISSREW 2014

PB - Institute of Electrical and Electronics Engineers Inc.

ER -