fault-injection capabilities (v3)
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest8 patches 16 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/8 | documentation and scriptsDocumentation/ Documentation/ Documentation/ | +186 | 2 replies | |
| 2/8 | fault-injection capabilities infrastructureinclude/ lib/ lib/ +1 more | +130 | 2 replies | |
| 3/8 | fault-injection capability for kmallocinclude/ lib/ mm/ | +45 | 0 replies | |
| 4/8 | fault-injection capability for alloc_pages()include/ lib/ mm/ | +45 | 0 replies | |
| 5/8 | fault-injection capability for disk IOblock/ block/ fs/ +3 more | +107 | 0 replies | |
| 6/8 | debugfs entries for configurationlib/ lib/ lib/ | +188 | 1 reply | |
| 7/8 | process filtering for fault-injection capabilitiesfs/ include/ include/ +1 more | +96 | 4 replies | |
| 8/8 | stacktrace filtering for fault-injection capabilitiesinclude/ lib/ lib/ +1 more | +120 | 7 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [patch 0/8] fault-injection capabilities (v3)
Changes from last version
- add stacktrace filter
- drop process-filter from boot-time setup
- build fixes from Don Mullis
- add documentation and some scripts
---
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_FAULT_INJECTION_DEBUGFS)
2. build and boot with this kernel
3. modprobe fault-inject-debugfs
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.
/debug/failslab/process-filter
specifies whether process filter is enabled or not.
it allows failing only permitted processes by /proc/<pid>/make-it-fail
/debug/failslab/stacktrace-depth
specifies the maximum stacktrace depth walking allowed. a value '0' means stacktrace filter is disabled.
/debug/failslab/address-start
/debug/failslab/address-end
specifies the range of virtual address.
it allows failing only if the stacktrace hits in this range.
5. see what really happens.