public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Akinobu Mita <akinobu.mita@gmail.com>
To: linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Cc: Akinobu Mita <akinobu.mita@gmail.com>
Subject: [PATCH v2 0/5] notifier error injection
Date: Mon, 18 Jul 2011 10:16:01 +0900	[thread overview]
Message-ID: <1310951766-3840-1-git-send-email-akinobu.mita@gmail.com> (raw)

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

Changelog:

* 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
- make CONFIG_PM_NOTIFIER_ERROR_INJECTION default if PM_DEBUG is enabled

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(-)

-- 
1.7.4.4


             reply	other threads:[~2011-07-18  1:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-18  1:16 Akinobu Mita [this message]
2011-07-18  1:16 ` [PATCH v2 1/5] fault-injection: notifier error injection Akinobu Mita
2011-07-18  1:16 ` [PATCH v2 2/5] cpu: CPU " Akinobu Mita
2011-07-18  8:29   ` Américo Wang
2011-07-18  9:42     ` Akinobu Mita
2011-07-18  1:16 ` [PATCH v2 3/5] PM: PM " Akinobu Mita
2011-07-18  1:16 ` [PATCH v2 4/5] memory: memory " Akinobu Mita
2011-07-18  1:16 ` [PATCH v2 5/5] powerpc: pSeries reconfig " Akinobu Mita
2011-07-21 21:37 ` [PATCH v2 0/5] " Andrew Morton
2011-07-22  4:18   ` Américo Wang
2011-07-22  4:49   ` Akinobu Mita

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1310951766-3840-1-git-send-email-akinobu.mita@gmail.com \
    --to=akinobu.mita@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox