linux-toradex.git/Documentation/fault-injection, branch v3.10.2

doc: fix quite a few typos within Documentation

2012-11-19T13:28:24+00:00

Correct spelling typo in Documentations

Signed-off-by: Jiri Kosina

fault-injection: add tool to run command with failslab or fail_page_alloc

2012-07-31T00:25:22+00:00

This adds tools/testing/fault-injection/failcmd.sh to run a command while
injecting slab/page allocation failures via fault injection.

Example:

Run a command "make -C tools/testing/selftests/ run_tests" with
injecting slab allocation failure.

	# ./tools/testing/fault-injection/failcmd.sh \
		-- make -C tools/testing/selftests/ run_tests

Same as above except to specify 100 times failures at most instead of
one time at most by default.

	# ./tools/testing/fault-injection/failcmd.sh --times=100 \
		-- make -C tools/testing/selftests/ run_tests

Same as above except to inject page allocation failure instead of slab
allocation failure.

	# env FAILCMD_TYPE=fail_page_alloc \
		./tools/testing/fault-injection/failcmd.sh --times=100 \
		-- make -C tools/testing/selftests/ run_tests

Signed-off-by: Akinobu Mita 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

fault-injection: notifier error injection

2012-07-31T00:25:22+00:00

This patchset provides kernel modules that can be used to test the error
handling of notifier call chain failures by injecting artifical errors to
the following notifier chain callbacks.

 * CPU notifier
 * PM notifier
 * memory hotplug notifier
 * powerpc pSeries reconfig notifier

Example: Inject CPU offline error (-1 == -EPERM)

  # cd /sys/kernel/debug/notifier-error-inject/cpu
  # echo -1 > actions/CPU_DOWN_PREPARE/error
  # echo 0 > /sys/devices/system/cpu/cpu1/online
  bash: echo: write error: Operation not permitted

The patchset also adds cpu and memory hotplug tests to
tools/testing/selftests These tests first do simple online and offline
test and then do fault injection tests if notifier error injection
module is available.

This patch:

The notifier error injection provides the ability to inject artifical
errors to specified notifier chain callbacks.  It is useful to test the
error handling of notifier call chain failures.

This adds common basic functions to define which type of events can be
fail and to initialize the debugfs interface to control what error code
should be returned and which event should be failed.

Signed-off-by: Akinobu Mita 
Cc: Pavel Machek 
Cc: "Rafael J. Wysocki" 
Cc: Greg KH 
Cc: Benjamin Herrenschmidt 
Cc: Paul Mackerras 
Cc: Michael Ellerman 
Cc: Dave Jones 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

fault-injection: update documentation with the mmc module param

2011-10-26T20:32:13+00:00

Signed-off-by: Per Forlin 
Reviewed-by: Akinobu Mita 
Signed-off-by: Chris Ball

fault-inject: add documentation on MMC IO fault injection

2011-10-26T19:43:34+00:00

Add description on how to enable random fault injection
for MMC IO.

Signed-off-by: Per Forlin 
Acked-by: Akinobu Mita 
Reviewed-by: Linus Walleij 
Signed-off-by: Chris Ball

fault-injection: add ability to export fault_attr in arbitrary directory

2011-08-04T00:25:20+00:00

init_fault_attr_dentries() is used to export fault_attr via debugfs.
But it can only export it in debugfs root directory.

Per Forlin is working on mmc_fail_request which adds support to inject
data errors after a completed host transfer in MMC subsystem.

The fault_attr for mmc_fail_request should be defined per mmc host and
export it in debugfs directory per mmc host like
/sys/kernel/debug/mmc0/mmc_fail_request.

init_fault_attr_dentries() doesn't help for mmc_fail_request.  So this
introduces fault_create_debugfs_attr() which is able to create a
directory in the arbitrary directory and replace
init_fault_attr_dentries().

[akpm@linux-foundation.org: extraneous semicolon, per Randy]
Signed-off-by: Akinobu Mita 
Tested-by: Per Forlin 
Cc: Jens Axboe 
Cc: Christoph Lameter 
Cc: Pekka Enberg 
Cc: Matt Mackall 
Cc: Randy Dunlap 
Cc: Stephen Rothwell 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

lkdtm: add debugfs access and loosen KPROBE ties

2010-03-06T19:26:32+00:00

Add adds a debugfs interface and additional failure modes to LKDTM to
provide similar functionality to the provoke-crash driver submitted here:

  http://lwn.net/Articles/371208/

Crashes can now be induced either through module parameters (as before)
or through the debugfs interface as in provoke-crash.

The patch also provides a new "direct" interface, where KPROBES are not
used, i.e., the crash is invoked directly upon write to the debugfs
file. When built without KPROBES configured, only this mode is available.

Signed-off-by: Simon Kagstrom 
Cc: M. Mohan Kumar 
Cc: Americo Wang 
Cc: David Woodhouse 
Cc: Ingo Molnar 
Cc: "Eric W. Biederman" ,
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

fault injection: correct function names in documentation

2010-02-03T02:11:22+00:00

init_fault_attr_entries() should be init_fault_attr_dentries().

cleanup_fault_attr_entries() should be cleanup_fault_attr_dentries().

Signed-off-by: Anton Blanchard 
Acked-by: Akinobu Mita 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

debugfs: Fix terminology inconsistency of dir name to mount debugfs filesystem.

2009-06-16T04:30:28+00:00

Many developers use "/debug/" or "/debugfs/" or "/sys/kernel/debug/"
directory name to mount debugfs filesystem for ftrace according to
./Documentation/tracers/ftrace.txt file.

And, three directory names(ex:/debug/, /debugfs/, /sys/kernel/debug/) is
existed in kernel source like ftrace, DRM, Wireless, Documentation,
Network[sky2]files to mount debugfs filesystem.

debugfs means debug filesystem for debugging easy to use by greg kroah
hartman. "/sys/kernel/debug/" name is suitable as directory name
of debugfs filesystem.
- debugfs related reference: http://lwn.net/Articles/334546/

Fix inconsistency of directory name to mount debugfs filesystem.

* From Steven Rostedt
  - find_debugfs() and tracing_files() in this patch.

Signed-off-by: GeunSik Lim 
Acked-by     : Inaky Perez-Gonzalez 
Reviewed-by  : Steven Rostedt 
Reviewed-by  : James Smart 
CC: Jiri Kosina 
CC: David Airlie 
CC: Peter Osterlund 
CC: Ananth N Mavinakayanahalli 
CC: Anil S Keshavamurthy 
CC: Masami Hiramatsu 
Signed-off-by: Greg Kroah-Hartman

fault-injection: fix example scripts in documentation

2007-07-16T16:05:45+00:00

Fix and cleanup example scripts in fault injection documentation.

1. Eliminate broken oops() shell function.

2. Fold failcmd.sh and failmodule.sh into example scripts. It makes
   the example scripts work independent of current working directory.

3. Set "space" parameter to 0 to start injecting errors immediately.

4. Use /sys/module//sections/.data as upper bound of
   .text section. Because some module doesn't have .exit.text section.

Signed-off-by: Akinobu Mita 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds