1 Fault injection capabilities infrastructure
2 ===========================================
4 See also drivers/md/faulty.c and "every_nth" module option for scsi_debug.
7 Available fault injection capabilities
8 --------------------------------------
12 injects slab allocation failures. (kmalloc(), kmem_cache_alloc(), ...)
16 injects page allocation failures. (alloc_pages(), get_free_pages(), ...)
20 injects disk IO errors on devices permitted by setting
21 /sys/block/<device>/make-it-fail or
22 /sys/block/<device>/<partition>/make-it-fail. (generic_make_request())
24 Configure fault-injection capabilities behavior
25 -----------------------------------------------
29 fault-inject-debugfs kernel module provides some debugfs entries for runtime
30 configuration of fault-injection capabilities.
32 - /debug/fail*/probability:
34 likelihood of failure injection, in percent.
37 Note that one-failure-per-hundred is a very high error rate
38 for some testcases. Consider setting probability=100 and configure
39 /debug/fail*/interval for such testcases.
41 - /debug/fail*/interval:
43 specifies the interval between failures, for calls to
44 should_fail() that pass all the other tests.
46 Note that if you enable this, by setting interval>1, you will
47 probably want to set probability=100.
51 specifies how many times failures may happen at most.
52 A value of -1 means "no limit".
56 specifies an initial resource "budget", decremented by "size"
57 on each call to should_fail(,size). Failure injection is
58 suppressed until "space" reaches zero.
60 - /debug/fail*/verbose
63 specifies the verbosity of the messages when failure is
64 injected. '0' means no messages; '1' will print only a single
65 log line per failure; '2' will print a call trace too -- useful
66 to debug the problems revealed by fault injection.
68 - /debug/fail*/task-filter:
71 A value of 'N' disables filtering by process (default).
72 Any positive value limits failures to only processes indicated by
73 /proc/<pid>/make-it-fail==1.
75 - /debug/fail*/require-start:
76 - /debug/fail*/require-end:
77 - /debug/fail*/reject-start:
78 - /debug/fail*/reject-end:
80 specifies the range of virtual addresses tested during
81 stacktrace walking. Failure is injected only if some caller
82 in the walked stacktrace lies within the required range, and
83 none lies within the rejected range.
84 Default required range is [0,ULONG_MAX) (whole of virtual address space).
85 Default rejected range is [0,0).
87 - /debug/fail*/stacktrace-depth:
89 specifies the maximum stacktrace depth walked during search
90 for a caller within [require-start,require-end) OR
91 [reject-start,reject-end).
93 - /debug/fail_page_alloc/ignore-gfp-highmem:
96 default is 'N', setting it to 'Y' won't inject failures into
97 highmem/user allocations.
99 - /debug/failslab/ignore-gfp-wait:
100 - /debug/fail_page_alloc/ignore-gfp-wait:
102 Format: { 'Y' | 'N' }
103 default is 'N', setting it to 'Y' will inject failures
104 only into non-sleep allocations (GFP_ATOMIC allocations).
108 In order to inject faults while debugfs is not available (early boot time),
113 fail_make_request=<interval>,<probability>,<space>,<times>
115 How to add new fault injection capability
116 -----------------------------------------
118 o #include <linux/fault-inject.h>
120 o define the fault attributes
122 DECLARE_FAULT_INJECTION(name);
124 Please see the definition of struct fault_attr in fault-inject.h
127 o provide a way to configure fault attributes
131 If you need to enable the fault injection capability from boot time, you can
132 provide boot option to configure it. There is a helper function for it:
134 setup_fault_attr(attr, str);
138 failslab, fail_page_alloc, and fail_make_request use this way.
141 init_fault_attr_entries(entries, attr, name);
142 void cleanup_fault_attr_entries(entries);
146 If the scope of the fault injection capability is limited to a
147 single kernel module, it is better to provide module parameters to
148 configure the fault attributes.
150 o add a hook to insert failures
152 Upon should_fail() returning true, client code should inject a failure.
154 should_fail(attr, size);
159 o inject slab allocation failures into module init/cleanup code
161 ------------------------------------------------------------------------------
164 FAILCMD=Documentation/fault-injection/failcmd.sh
165 BLACKLIST="root_plug evbug"
168 echo Y > /debug/$FAILNAME/task-filter
169 echo 10 > /debug/$FAILNAME/probability
170 echo 100 > /debug/$FAILNAME/interval
171 echo -1 > /debug/$FAILNAME/times
172 echo 2 > /debug/$FAILNAME/verbose
173 echo 1 > /debug/$FAILNAME/ignore-gfp-wait
177 echo $BLACKLIST | grep $1 > /dev/null 2>&1
182 dmesg | grep BUG > /dev/null 2>&1
185 find /lib/modules/`uname -r` -name '*.ko' -exec basename {} .ko \; |
193 bash $FAILCMD modprobe $i
197 lsmod | awk '{ if ($3 == 0) { print $1 } }' |
205 bash $FAILCMD modprobe -r $i
209 ------------------------------------------------------------------------------
211 o inject slab allocation failures only for a specific module
213 ------------------------------------------------------------------------------
216 FAILMOD=Documentation/fault-injection/failmodule.sh
218 echo injecting errors into the module $1...
221 bash $FAILMOD failslab $1 10
222 echo 25 > /debug/failslab/probability
224 ------------------------------------------------------------------------------