diff options
| author |   Paul E. McKenney <paulmck@linux.vnet.ibm.com> | 2017-10-19 14:52:41 -0700 |
|---|---|---|
| committer | Paul E. McKenney <paulmck@linux.vnet.ibm.com> | 2017-12-11 09:17:39 -0800 |
| commit | efd88b02bb9e6b8b73a20ea611e5d07ed6d4af34 (patch) | |
| tree | 0f84096dc8cc757f5c0c8b7c9de51dec0ccd9342 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | tracing, rcu: Hide trace event rcu_nocb_wake when not used (diff) | |
| download | wireguard-linux-efd88b02bb9e6b8b73a20ea611e5d07ed6d4af34.tar.xz wireguard-linux-efd88b02bb9e6b8b73a20ea611e5d07ed6d4af34.zip | |
rcu: Add comment giving debug strategy for double call_rcu()
The following statement has for some reason proven non-intuitive:
WARN_ON_ONCE(rcu_segcblist_empty(&rdp->cblist) != (count == 0));
This commit therefore adds a comment that states that this warning
usually triggers in response to a double call_rcu(), which is sort
of like a double free. The comment also suggests building with
CONFIG_DEBUG_OBJECTS_RCU_HEAD=y to track down the double call_rcu().
Reported-by: David Howells <dhowells@redhat.com>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions