From: Andrew Morton <akpm@linux-foundation.org>
To: Akinobu Mita <akinobu.mita@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/5] notifier error injection
Date: Thu, 21 Jul 2011 14:37:09 -0700 [thread overview]
Message-ID: <20110721143709.0c1e66d6.akpm@linux-foundation.org> (raw)
In-Reply-To: <1310951766-3840-1-git-send-email-akinobu.mita@gmail.com>
On Mon, 18 Jul 2011 10:16:01 +0900
Akinobu Mita <akinobu.mita@gmail.com> wrote:
> 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.
That all looks very nice, but I wonder how many people are actually
using these things. The injection framework itself doesn't seem to
have had a lot of uptake.
I wonder if we could improve things by adding an easy-to-run testing
script which identifies all the available error-injection inputs,
exercises them and then reports on the result?
Such a script would logically reside under ./tests/fault-injection/,
but we still don't have a tests/ directory. Which perhaps tells us
something ;)
next prev parent reply other threads:[~2011-07-21 21:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-18 1:16 [PATCH v2 0/5] notifier error injection Akinobu Mita
2011-07-18 1:16 ` [PATCH v2 1/5] fault-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 ` Andrew Morton [this message]
2011-07-22 4:18 ` [PATCH v2 0/5] " 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=20110721143709.0c1e66d6.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=akinobu.mita@gmail.com \
--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