tree/tiny rcu: Add debug RCU head objects (v5)
in [Kernel]
|
Prev: [PATCH] Security: Fix the comment of cap_file_mmap()
Next: [PATCH] mc13783-regulator: fix a memory leak in mc13783_regulator_remove
From: Lai Jiangshan on 18 Apr 2010 21:20 Reviewed-by: Lai Jiangshan <laijs(a)cn.fujitsu.com> Mathieu Desnoyers wrote: > Helps finding racy users of call_rcu(), which results in hangs because list > entries are overwritten and/or skipped. > > Changelog since v4: > - Bissectability is now OK > - Now generate a WARN_ON_ONCE() for non-initialized rcu_head passed to > call_rcu(). Statically initialized objects are detected with > object_is_static(). > - Rename rcu_head_init_on_stack to init_rcu_head_on_stack. > - Remove init_rcu_head() completely. > > Changelog since v3: > - Include comments from Lai Jiangshan > -- 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/
From: Paul E. McKenney on 19 Apr 2010 09:40
On Mon, Apr 19, 2010 at 09:17:58AM +0800, Lai Jiangshan wrote: > > Reviewed-by: Lai Jiangshan <laijs(a)cn.fujitsu.com> Thank you, Lai!!! I have added your Reviewed-by. Thanx, Paul > Mathieu Desnoyers wrote: > > Helps finding racy users of call_rcu(), which results in hangs because list > > entries are overwritten and/or skipped. > > > > Changelog since v4: > > - Bissectability is now OK > > - Now generate a WARN_ON_ONCE() for non-initialized rcu_head passed to > > call_rcu(). Statically initialized objects are detected with > > object_is_static(). > > - Rename rcu_head_init_on_stack to init_rcu_head_on_stack. > > - Remove init_rcu_head() completely. > > > > Changelog since v3: > > - Include comments from Lai Jiangshan > > -- 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/ |