On Sat, 13 Feb 2016 00:47:08 +0100 Sebastian Andrzej Siewior wrote: > - There is a useless rcu_bh thread which has been deactivated. > For some strange reason I had RCU_TORTURE_TEST defined in my config. This caused my compile to blow up because kernel/rcu/rcutorture.c wanted to test the (now ifdef'ed out) rcu_bh routines. This fixes the compile issue but is untested for actually *running* rcutorture. I'll try that on a test box tomorrow. Clark From a835ff3aad772520d34548dc336925788a649b17 Mon Sep 17 00:00:00 2001 From: Clark Williams Date: Mon, 15 Feb 2016 22:48:04 -0600 Subject: [PATCH] rcutorture: comment out rcu_bh ops on PREEMPT_RT_FULL RT has dropped support of rcu_bh, comment out in rcutorture. Signed-off-by: Clark Williams --- kernel/rcu/rcutorture.c | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/kernel/rcu/rcutorture.c b/kernel/rcu/rcutorture.c index d89328e260df..5bb3364a6284 100644 --- a/kernel/rcu/rcutorture.c +++ b/kernel/rcu/rcutorture.c @@ -390,6 +390,7 @@ static struct rcu_torture_ops rcu_ops = { .name = "rcu" }; +#ifndef CONFIG_PREEMPT_RT_FULL /* * Definitions for rcu_bh torture testing. */ @@ -429,6 +430,12 @@ static struct rcu_torture_ops rcu_bh_ops = { .name = "rcu_bh" }; +#else +static struct rcu_torture_ops rcu_bh_ops = { + .ttype = INVALID_RCU_FLAVOR, +}; +#endif + /* * Don't even think about trying any of these in real life!!! * The names includes "busted", and they really means it! -- 2.5.0