[PATCH v2 0/5] notifier error injection

From: Akinobu Mita
Date: Sun Jul 17 2011 - 21:14:32 EST

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

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

We already have cpu-notifier-error-inject.ko module providing such
functionality for the CPU notifier. However, this patch set adds
common basic functions and consistent debugfs interface for them.

Each of the files in the directory represents an event which can be
failed and contains the error code. If the notifier call chain should
be failed with some events notified, write the error code to the files.

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

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


* v2
- "PM: Improve error code of pm_notifier_call_chain()" is now in -next
- "debugfs: add debugfs_create_int" is dropped
- put a comment in err_inject_notifier_block_init()
- only allow valid errno to be injected (-MAX_ERRNO <= errno <= 0)
- improve Kconfig help text
- make CONFIG_PM_NOTIFIER_ERROR_INJECTION visible even if PM_DEBUG is disabled

Akinobu Mita (5):
fault-injection: notifier error injection
cpu: CPU notifier error injection
PM: PM notifier error injection
memory: memory notifier error injection
powerpc: pSeries reconfig notifier error injection

Documentation/feature-removal-schedule.txt | 8 +++
arch/powerpc/platforms/pseries/reconfig.c | 31 +++++++++++
drivers/base/memory.c | 29 ++++++++++
include/linux/notifier.h | 25 +++++++++
kernel/cpu.c | 31 +++++++++++
kernel/notifier.c | 81 ++++++++++++++++++++++++++++
kernel/power/main.c | 30 ++++++++++
lib/Kconfig.debug | 71 ++++++++++++++++++++++++
8 files changed, 306 insertions(+), 0 deletions(-)


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/