Hi Cyril, Wanlong and all,
This is the latest version of mm/zram01 testcase fixes. Current
zram01 test has mulitple issues:
a) typo error
b) it fails to give correct behavior if zram not mounted.
c) it fails to repeat the test due to reset operation comes too early;
d) it doesn't check whether the bytes written to zram device is valid or not
e) it fails to unload the module due to memory still possesses zram device;
The patch series contains the following patches:
[PATCH v5 1/7] mm/zram01: fix memset() parameters
[PATCH v5 2/7] mm/zram01: errno not captured
[PATCH v5 3/7] mm/zram01: split test steps into functions
[PATCH v5 4/7] mm/zram01: write memory to zram device
[PATCH v5 5/7] mm/zram01: unmap it after memory written to device
[PATCH v5 6/7] mm/zram01: verify content written to zram
[PATCH v5 7/7] mm/zram01: change int to long to avoid overflow
Note that patch 3,4,6 solved issue c) and d) at the same time, since content
verification step will delay reset operation.
Now the new case could be working quite stable under the following test
scenarios:
- zram not loaded before test, run zram01 test once;
- zram not loaded before test, run zram01 test for multiple times (w/ -i);
- zram loaded before test, run zram01 test once (not unload after test);
- zram loaded before test, run zram01 test for multiple times.
Thanks,
Caspar
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
