Hi Paul, Please find the following patches which enable RCU early boot tests. For now all we do in these tests are enqueue test callbacks and check if they are being invoked or not.
I was able to reproduce the hang which Amit reported after reverting the fix. So this should catch such errors if they occur in the future. I enabled the selftests in a few rcutorture configurations. Thanks! -- Pranith Pranith Kumar (3): rcu: Add early boot self tests doc: Document RCU self test boot params rcutorture: Enable RCU self test in configs Documentation/kernel-parameters.txt | 12 +++ kernel/rcu/rcu.h | 2 + kernel/rcu/tiny.c | 4 +- kernel/rcu/tree.c | 2 + kernel/rcu/update.c | 91 ++++++++++++++++++++++ .../selftests/rcutorture/configs/rcu/TINY02 | 2 + .../selftests/rcutorture/configs/rcu/TINY02.boot | 2 + .../selftests/rcutorture/configs/rcu/TREE05.boot | 1 + .../selftests/rcutorture/configs/rcu/TREE06.boot | 4 + .../selftests/rcutorture/configs/rcu/TREE08 | 2 + .../selftests/rcutorture/configs/rcu/TREE08.boot | 2 + 11 files changed, 123 insertions(+), 1 deletion(-) create mode 100644 tools/testing/selftests/rcutorture/configs/rcu/TINY02.boot create mode 100644 tools/testing/selftests/rcutorture/configs/rcu/TREE06.boot -- 2.1.0 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
