Prev: [PATCH tip/core/rcu 07/21] sched: better name for for_each_domain_rd
Next: [PATCH tip/core/rcu 08/21] vfs: apply lockdep-based checking to rcu_dereference() uses
From: Paul E. McKenney on 22 Feb 2010 20:10
The current "mod_timer(&t, 1)" potentially makes the timer fire immediately,
change this to wait one jiffy.

Signed-off-by: Dan Carpenter <error27(a)gmail.com>
Signed-off-by: Paul E. McKenney <paulmck(a)linux.vnet.ibm.com>
---
kernel/rcutorture.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/kernel/rcutorture.c b/kernel/rcutorture.c
index 5f43f30..258cdf0 100644
--- a/kernel/rcutorture.c
+++ b/kernel/rcutorture.c
@@ -853,7 +853,7 @@ rcu_torture_reader(void *arg)
do {
if (irqreader && cur_ops->irq_capable) {
if (!timer_pending(&t))
- mod_timer(&t, 1);
+ mod_timer(&t, jiffies + 1);
}
idx = cur_ops->readlock();
completed = cur_ops->completed();
--
1.6.6

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [PATCH tip/core/rcu 07/21] sched: better name for for_each_domain_rd
Next: [PATCH tip/core/rcu 08/21] vfs: apply lockdep-based checking to rcu_dereference() uses