From: Akinobu Mita <akinobu.mita@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: ak@suse.de, akpm@osdl.org, Don Mullis <dwm@meer.net>
Subject: [patch 0/7] Fault-injection capabilities (v6)
Date: Thu, 09 Nov 2006 02:45:41 +0900 [thread overview]
Message-ID: <455217df.719dec4f.2c80.ffffb500@mx.google.com> (raw)
Fault-injection capabilities patch set version 6.
Please read the mail for the patch 1/7 for details
Changes from the last version
- add /debug/{failslab,fail_page_alloc}/ignore-gfp-highmem
to let fault-injector ignore highmem/user allocations
- add /debug/{failslab,fail_page_alloc}/ignore-gfp-wait
to let fault-injector ignore sleepable allocations.
- use random32() for lightweight random simlator
- update documentation and scripts
next reply other threads:[~2006-11-08 17:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 17:45 Akinobu Mita [this message]
2006-11-20 3:04 ` [PATCH -mm] fault-injection: reject-failure-if-any-caller-lies-within-specified range Don Mullis
2006-11-20 10:57 ` Akinobu Mita
2006-11-20 19:24 ` Don Mullis
2006-11-20 19:52 ` 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=455217df.719dec4f.2c80.ffffb500@mx.google.com \
--to=akinobu.mita@gmail.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=dwm@meer.net \
--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