Abstract
This paper describes an experimental study of Linux kernel behavior in the presence of errors that impact the instruction stream of the kernel code. Extensive error injection experiments including over 35,000 errors are conducted targeting the most frequently used functions in the selected kernel subsystems. Three types of faults/errors injection campaigns are conducted: (1) random non-branch instruction, (2) random conditional branch, and (3) valid but incorrect branch. The analysis of the obtained data shows: (i) 95% of the crashes are due to four major causes, namely, unable to handle kernel NULL pointer, unable to handle kernel paging request, invalid opcode, and general protection fault, (ii) less than 10% of the crashes are associated with fault propagation and nearly 40% of crash latencies are within 10 cycles, (iii) errors in the kernel can result in crashes that require reformatting the file system to restore system operation; the process of bringing up the system can take nearly an hour.
| Original language | English (US) |
|---|---|
| Pages | 459-468 |
| Number of pages | 10 |
| State | Published - Dec 1 2003 |
| Event | 2003 International Conference on Dependable Systems and Networks - San Francisco, CA, United States Duration: Jun 22 2003 → Jun 25 2003 |
Other
| Other | 2003 International Conference on Dependable Systems and Networks |
|---|---|
| Country | United States |
| City | San Francisco, CA |
| Period | 6/22/03 → 6/25/03 |
Fingerprint
ASJC Scopus subject areas
- Software
- Hardware and Architecture
- Computer Networks and Communications
Cite this
Characterization of Linux Kernel Behavior under Errors. / Gu, Weining; Kalbarczyk, Zbigniew; Iyer, Ravishankar K.; Yang, Zhenyu.
2003. 459-468 Paper presented at 2003 International Conference on Dependable Systems and Networks, San Francisco, CA, United States.Research output: Contribution to conference › Paper
}
TY - CONF
T1 - Characterization of Linux Kernel Behavior under Errors
AU - Gu, Weining
AU - Kalbarczyk, Zbigniew
AU - Iyer, Ravishankar K.
AU - Yang, Zhenyu
PY - 2003/12/1
Y1 - 2003/12/1
N2 - This paper describes an experimental study of Linux kernel behavior in the presence of errors that impact the instruction stream of the kernel code. Extensive error injection experiments including over 35,000 errors are conducted targeting the most frequently used functions in the selected kernel subsystems. Three types of faults/errors injection campaigns are conducted: (1) random non-branch instruction, (2) random conditional branch, and (3) valid but incorrect branch. The analysis of the obtained data shows: (i) 95% of the crashes are due to four major causes, namely, unable to handle kernel NULL pointer, unable to handle kernel paging request, invalid opcode, and general protection fault, (ii) less than 10% of the crashes are associated with fault propagation and nearly 40% of crash latencies are within 10 cycles, (iii) errors in the kernel can result in crashes that require reformatting the file system to restore system operation; the process of bringing up the system can take nearly an hour.
AB - This paper describes an experimental study of Linux kernel behavior in the presence of errors that impact the instruction stream of the kernel code. Extensive error injection experiments including over 35,000 errors are conducted targeting the most frequently used functions in the selected kernel subsystems. Three types of faults/errors injection campaigns are conducted: (1) random non-branch instruction, (2) random conditional branch, and (3) valid but incorrect branch. The analysis of the obtained data shows: (i) 95% of the crashes are due to four major causes, namely, unable to handle kernel NULL pointer, unable to handle kernel paging request, invalid opcode, and general protection fault, (ii) less than 10% of the crashes are associated with fault propagation and nearly 40% of crash latencies are within 10 cycles, (iii) errors in the kernel can result in crashes that require reformatting the file system to restore system operation; the process of bringing up the system can take nearly an hour.
UR - http://www.scopus.com/inward/record.url?scp=1542359963&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=1542359963&partnerID=8YFLogxK
M3 - Paper
AN - SCOPUS:1542359963
SP - 459
EP - 468
ER -