fault-injection.txt 6.4 KB
Newer Older
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Fault injection capabilities infrastructure
===========================================

See also drivers/md/faulty.c and "every_nth" module option for scsi_debug.


Available fault injection capabilities
--------------------------------------

o failslab

  injects slab allocation failures. (kmalloc(), kmem_cache_alloc(), ...)

o fail_page_alloc

  injects page allocation failures. (alloc_pages(), get_free_pages(), ...)

o fail_make_request

20
  injects disk IO errors on devices permitted by setting
21 22 23 24 25 26 27 28 29 30 31
  /sys/block/<device>/make-it-fail or
  /sys/block/<device>/<partition>/make-it-fail. (generic_make_request())

Configure fault-injection capabilities behavior
-----------------------------------------------

o debugfs entries

fault-inject-debugfs kernel module provides some debugfs entries for runtime
configuration of fault-injection capabilities.

32
- /sys/kernel/debug/fail*/probability:
33 34 35 36

	likelihood of failure injection, in percent.
	Format: <percent>

37 38
	Note that one-failure-per-hundred is a very high error rate
	for some testcases.  Consider setting probability=100 and configure
39
	/sys/kernel/debug/fail*/interval for such testcases.
40

41
- /sys/kernel/debug/fail*/interval:
42 43 44 45 46 47 48

	specifies the interval between failures, for calls to
	should_fail() that pass all the other tests.

	Note that if you enable this, by setting interval>1, you will
	probably want to set probability=100.

49
- /sys/kernel/debug/fail*/times:
50 51 52 53

	specifies how many times failures may happen at most.
	A value of -1 means "no limit".

54
- /sys/kernel/debug/fail*/space:
55 56 57 58 59

	specifies an initial resource "budget", decremented by "size"
	on each call to should_fail(,size).  Failure injection is
	suppressed until "space" reaches zero.

60
- /sys/kernel/debug/fail*/verbose
61 62

	Format: { 0 | 1 | 2 }
63 64 65 66
	specifies the verbosity of the messages when failure is
	injected.  '0' means no messages; '1' will print only a single
	log line per failure; '2' will print a call trace too -- useful
	to debug the problems revealed by fault injection.
67

68
- /sys/kernel/debug/fail*/task-filter:
69

70 71
	Format: { 'Y' | 'N' }
	A value of 'N' disables filtering by process (default).
72 73 74
	Any positive value limits failures to only processes indicated by
	/proc/<pid>/make-it-fail==1.

75 76 77 78
- /sys/kernel/debug/fail*/require-start:
- /sys/kernel/debug/fail*/require-end:
- /sys/kernel/debug/fail*/reject-start:
- /sys/kernel/debug/fail*/reject-end:
79 80 81

	specifies the range of virtual addresses tested during
	stacktrace walking.  Failure is injected only if some caller
82 83 84 85
	in the walked stacktrace lies within the required range, and
	none lies within the rejected range.
	Default required range is [0,ULONG_MAX) (whole of virtual address space).
	Default rejected range is [0,0).
86

87
- /sys/kernel/debug/fail*/stacktrace-depth:
88 89

	specifies the maximum stacktrace depth walked during search
90 91
	for a caller within [require-start,require-end) OR
	[reject-start,reject-end).
92

93
- /sys/kernel/debug/fail_page_alloc/ignore-gfp-highmem:
94

95 96
	Format: { 'Y' | 'N' }
	default is 'N', setting it to 'Y' won't inject failures into
97 98
	highmem/user allocations.

99 100
- /sys/kernel/debug/failslab/ignore-gfp-wait:
- /sys/kernel/debug/fail_page_alloc/ignore-gfp-wait:
101

102 103
	Format: { 'Y' | 'N' }
	default is 'N', setting it to 'Y' will inject failures
104 105
	only into non-sleep allocations (GFP_ATOMIC allocations).

106
- /sys/kernel/debug/fail_page_alloc/min-order:
107 108 109 110

	specifies the minimum page allocation order to be injected
	failures.

111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131
o Boot option

In order to inject faults while debugfs is not available (early boot time),
use the boot option:

	failslab=
	fail_page_alloc=
	fail_make_request=<interval>,<probability>,<space>,<times>

How to add new fault injection capability
-----------------------------------------

o #include <linux/fault-inject.h>

o define the fault attributes

  DECLARE_FAULT_INJECTION(name);

  Please see the definition of struct fault_attr in fault-inject.h
  for details.

132
o provide a way to configure fault attributes
133 134 135 136

- boot option

  If you need to enable the fault injection capability from boot time, you can
137
  provide boot option to configure it. There is a helper function for it:
138

139
	setup_fault_attr(attr, str);
140 141 142 143

- debugfs entries

  failslab, fail_page_alloc, and fail_make_request use this way.
144
  Helper functions:
145

146
	fault_create_debugfs_attr(name, parent, attr);
147 148 149 150 151 152 153 154 155

- module parameters

  If the scope of the fault injection capability is limited to a
  single kernel module, it is better to provide module parameters to
  configure the fault attributes.

o add a hook to insert failures

156
  Upon should_fail() returning true, client code should inject a failure.
157

158
	should_fail(attr, size);
159 160 161 162

Application Examples
--------------------

163
o Inject slab allocation failures into module init/exit code
164 165 166

#!/bin/bash

167
FAILTYPE=failslab
168 169 170 171 172 173 174
echo Y > /sys/kernel/debug/$FAILTYPE/task-filter
echo 10 > /sys/kernel/debug/$FAILTYPE/probability
echo 100 > /sys/kernel/debug/$FAILTYPE/interval
echo -1 > /sys/kernel/debug/$FAILTYPE/times
echo 0 > /sys/kernel/debug/$FAILTYPE/space
echo 2 > /sys/kernel/debug/$FAILTYPE/verbose
echo 1 > /sys/kernel/debug/$FAILTYPE/ignore-gfp-wait
175

176
faulty_system()
177
{
178
	bash -c "echo 1 > /proc/self/make-it-fail && exec $*"
179 180
}

181 182 183 184 185 186 187 188 189 190
if [ $# -eq 0 ]
then
	echo "Usage: $0 modulename [ modulename ... ]"
	exit 1
fi

for m in $*
do
	echo inserting $m...
	faulty_system modprobe $m
191

192 193 194
	echo removing $m...
	faulty_system modprobe -r $m
done
195 196 197

------------------------------------------------------------------------------

198
o Inject page allocation failures only for a specific module
199 200 201

#!/bin/bash

202 203
FAILTYPE=fail_page_alloc
module=$1
204

205 206 207 208 209
if [ -z $module ]
then
	echo "Usage: $0 <modulename>"
	exit 1
fi
210

211
modprobe $module
212

213 214 215 216 217 218
if [ ! -d /sys/module/$module/sections ]
then
	echo Module $module is not loaded
	exit 1
fi

219 220
cat /sys/module/$module/sections/.text > /sys/kernel/debug/$FAILTYPE/require-start
cat /sys/module/$module/sections/.data > /sys/kernel/debug/$FAILTYPE/require-end
221

222 223 224 225 226 227 228 229 230
echo N > /sys/kernel/debug/$FAILTYPE/task-filter
echo 10 > /sys/kernel/debug/$FAILTYPE/probability
echo 100 > /sys/kernel/debug/$FAILTYPE/interval
echo -1 > /sys/kernel/debug/$FAILTYPE/times
echo 0 > /sys/kernel/debug/$FAILTYPE/space
echo 2 > /sys/kernel/debug/$FAILTYPE/verbose
echo 1 > /sys/kernel/debug/$FAILTYPE/ignore-gfp-wait
echo 1 > /sys/kernel/debug/$FAILTYPE/ignore-gfp-highmem
echo 10 > /sys/kernel/debug/$FAILTYPE/stacktrace-depth
231

232
trap "echo 0 > /sys/kernel/debug/$FAILTYPE/probability" SIGINT SIGTERM EXIT
233 234 235

echo "Injecting errors into the module $module... (interrupt to stop)"
sleep 1000000
236