On Sun, Jul 29, 2007 at 07:45:35PM -0700, Daniel Walker wrote: > Simple WARN_ON to catch any underflow in rcu_read_lock_nesting. > > Signed-off-by: Daniel Walker <[EMAIL PROTECTED]>
Acked-by: Paul E. McKenney <[EMAIL PROTECTED]> > --- > kernel/rcupreempt.c | 6 ++++++ > 1 file changed, 6 insertions(+) > > Index: linux-2.6.22/kernel/rcupreempt.c > =================================================================== > --- linux-2.6.22.orig/kernel/rcupreempt.c > +++ linux-2.6.22/kernel/rcupreempt.c > @@ -157,6 +157,12 @@ void __rcu_read_unlock(void) > } > > local_irq_restore(oldirq); > + > + /* > + * If our rcu_read_lock_nesting went negative, likely > + * something is wrong.. > + */ > + WARN_ON(current->rcu_read_lock_nesting < 0); > } > > static void __rcu_advance_callbacks(void) > > -- > - > To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html - 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/
