Torture-test changes for 4.11
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest9 patches 2 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/9 | torture: Add a check for CONFIG_RCU_STALL_COMMON for TINY01tools/ | +1 | 0 replies | |
| 2/9 | torture: Add CONFIG_PROVE_RCU_REPEATEDLY=y for TINY02tools/ | +1 | 0 replies | |
| 3/9 | torture: Add tests without slow grace period setup/cleanuptools/ tools/ tools/ +5 more | +21 | 0 replies | |
| 4/9 | torture: Run at least one test with CONFIG_DEBUG_OBJECTS_RCU_HEADtools/ | +1 | 0 replies | |
| 5/9 | torture: Run one test with DEBUG_LOCK_ALLOC but not PROVE_LOCKINGtools/ | +1 | 0 replies | |
| 6/9 | torture: Run a couple scenarios with CONFIG_RCU_EQS_DEBUGtools/ tools/ | +2 | 0 replies | |
| 7/9 | torture: Update RCU test scenario documentationtools/ | +31 | 0 replies | |
| 8/9 | locktorture: Fix potential memory leak with rw lock testkernel/ | +6 | 0 replies | |
| 9/9 | torture: Enable DEBUG_OBJECTS_RCU_HEAD for Tiny RCUtools/ | +1 | 0 replies |
Reviews trailers per patch
None of the 9 patches has a Reviewed-by or Acked-by of their own; the series has one for all of them.
| Patch | Josh Triplett |
|---|---|
| Series | R-b |
| 1/9 | |
| 2/9 | |
| 3/9 | |
| 4/9 | |
| 5/9 | |
| 6/9 | |
| 7/9 | |
| 8/9 | |
| 9/9 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH tip/core/rcu 0/9] Torture-test changes for 4.11
Hello!
This series provides torture-test updates:
1. Add a check for CONFIG_RCU_STALL_COMMON for TINY01, in order
to complain if this case is not tested.
2. Add CONFIG_PROVE_RCU_REPEATEDLY=y for TINY02, in order to test
this case.
3. Add tests without slow grace period setup/cleanup, as this case
is what is actually used in production.
4. Run at least one test with CONFIG_DEBUG_OBJECTS_RCU_HEAD, to make
sure that this case is tested regularly.
5. Run one test with DEBUG_LOCK_ALLOC but not PROVE_LOCKING, to make
sure that this case is tested regularly.
6. Run a couple scenarios with CONFIG_RCU_EQS_DEBUG, again to make
sure that this case is tested regularly.
7. Update RCU test scenario documentation.
8. Fix potential memory leak with rw lock test, courtesy of Yang Shi.
9. Enable DEBUG_OBJECTS_RCU_HEAD for Tiny RCU, you guessed it, to
make sure that this case is regularly tested.
Thanx, Paul
------------------------------------------------------------------------
kernel/locking/locktorture.c | 6 ++ tools/testing/selftests/rcutorture/configs/rcu/CFcommon | 3 - tools/testing/selftests/rcutorture/configs/rcu/TINY01 | 1 tools/testing/selftests/rcutorture/configs/rcu/TINY02 | 3 - tools/testing/selftests/rcutorture/configs/rcu/TREE01 | 3 + tools/testing/selftests/rcutorture/configs/rcu/TREE02 | 4 + tools/testing/selftests/rcutorture/configs/rcu/TREE03 | 3 + tools/testing/selftests/rcutorture/configs/rcu/TREE04 | 4 + tools/testing/selftests/rcutorture/configs/rcu/TREE05 | 3 + tools/testing/selftests/rcutorture/configs/rcu/TREE06 | 3 + tools/testing/selftests/rcutorture/configs/rcu/TREE07 | 3 + tools/testing/selftests/rcutorture/configs/rcu/TREE08 | 4 - tools/testing/selftests/rcutorture/doc/TREE_RCU-kconfig.txt | 33 +++++++++++- 13 files changed, 65 insertions(+), 8 deletions(-)