RFC: fault-injection capabilities
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest5 patches 14 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | fail-injection libraryinclude/ lib/ lib/ +1 more | +118 | 1 reply | |
| 2/5 | fail-injection capability for kmalloc.include/ lib/ mm/ | +31 | 0 replies | |
| 3/5 | fail-injection capability for alloc_pages()include/ lib/ mm/ | +31 | 0 replies | |
| 4/5 | fail-injection capability for disk IOblock/ include/ lib/ | +30 | 10 replies | |
| 5/5 | debugfs entries for configurationlib/ lib/ lib/ | +177 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [patch 0/5] RFC: fault-injection capabilities
This patch set provides some fault-injection capabilities.
- kmalloc failures
- alloc_pages() failures
- disk IO errors
We can see what really happens if those failures happen.
In order to enable these fault-injection capabilities:
1. Enable relevant config options (CONFIG_FAILSLAB, CONFIG_PAGE_ALLOC, CONFIG_MAKE_REQUEST) and runtime configuration kernel module (CONFIG_SHOULD_FAIL_KNOBS)
2. build and boot with this kernel
3. modprobe should_fail_knob
4. configure fault-injection capabilities behavior by debugfs
For example about kmalloc failures:
/debug/failslab/probability
specifies how often it should fail in percent.
/debug/failslab/interval
specifies the interval of failures.
/debug/failslab/times
specifies how many times failures may happen at most.
/debug/failslab/space
specifies the size of free space where memory can be allocated safely in bytes.
5. see what really happens.
The idea is taken from failmalloc (http://www.nongnu.org/failmalloc/).
Andrew Morton gave me interesting suggestions.
--