From: Dave Jones <davej@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Greg KH" <greg@kroah.com>,
"Akinobu Mita" <akinobu.mita@gmail.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
"Paul Mackerras" <paulus@samba.org>,
"Américo Wang" <xiyou.wangcong@gmail.com>,
linux-pm@lists.linux-foundation.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [linux-pm] [PATCH -v4 6/6] fault-injection: add notifier error injection testing scripts
Date: Tue, 26 Jun 2012 19:58:04 -0400 [thread overview]
Message-ID: <20120626235804.GA7525@redhat.com> (raw)
In-Reply-To: <20120626163147.93181e21.akpm@linux-foundation.org>
On Tue, Jun 26, 2012 at 04:31:47PM -0700, Andrew Morton wrote:
> My overall take on the fault-injection code is that there has been a
> disappointing amount of uptake: I don't see many developers using them
> for whitebox testing their stuff. I guess this patchset addresses
> that, in a way.
I added support for make-it-fail to my syscall fuzzer a while ago.
(if the file exists, the child processes set it before calling the fuzzed syscall).
I've not had a chance to really play with it, because I find enough problems
already even without it.
Dave
next prev parent reply other threads:[~2012-06-26 23:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-23 14:58 [PATCH -v4 0/6] notifier error injection Akinobu Mita
2012-06-23 14:58 ` [PATCH -v4 1/6] fault-injection: " Akinobu Mita
2012-06-23 14:58 ` [PATCH -v4 5/6] powerpc: pSeries reconfig notifier error injection module Akinobu Mita
2012-06-23 14:58 ` [PATCH -v4 6/6] fault-injection: add notifier error injection testing scripts Akinobu Mita
2012-06-26 23:31 ` Andrew Morton
2012-06-26 23:58 ` Dave Jones [this message]
2012-06-27 11:42 ` 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=20120626235804.GA7525@redhat.com \
--to=davej@redhat.com \
--cc=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=xiyou.wangcong@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).