tree b255fdc1c9839a864dfbd67916caef0efb5925a2
parent 2f6c9813f59c82214cadb47801858c42d6191866
author subrata_modak <subrata_modak> 1250944823 +0000
committer subrata_modak <subrata_modak> 1250944823 +0000

Introducing the "Kernel Fault Injection Framework" generation and testing capability in LTP. This is in line with the recent proposal made through LTP Paper at OLS 2009: "Putting LTP to test - Validating both the Linux kernel and Test-cases" (http://ltp.sourceforge.net/documentation/technical_papers/Putting_LTP_to_Test.pdf). This infrasturcture will help LTP directly in the following ways:
1) Allow test developers to test their new test cases against a faulted kernel, and then compare it on stable kernel run, impacting in better test development,
2) Allow test engineers to be able to generate more code coverage by traversing the rarely touched parts of the kernel code,
As we move forward in using this, we would definitely find some other advantages of this framework. This is V2 of patchset after incorporating comments from Mike, Paul & Garret.
[PATCH v2 01/05] Provide all necessary information through ltp/README: Provide all necessary information to create/use "Fault Injection Framework" through ltp/README. This is necessary before any test case(s) can be run on this harness. Also describes the general algorithm that would be followed while running LTP tests in "Fault Injection" harness. Changed the debugfs mount point from /debug/ to /sys/kernel/debug/ as pointed out by Mike. Signed-off-by: Subrata Modak<subrata@linux.vnet.ibm.com>.