summaryrefslogtreecommitdiffstats
path: root/net
diff options
context:
space:
mode:
authorHerbert Xu <herbert@gondor.apana.org.au>2005-10-23 16:11:39 +1000
committerHerbert Xu <herbert@gondor.apana.org.au>2005-10-23 16:11:39 +1000
commit203755029e063066ecc4cf5eee1110ab946c2d88 (patch)
tree2f57df251c75847c7fe6e5c694319553733812b9 /net
parentd475f3f47a0427dfee483cecf9a7e9109e991423 (diff)
downloadop-kernel-dev-203755029e063066ecc4cf5eee1110ab946c2d88.zip
op-kernel-dev-203755029e063066ecc4cf5eee1110ab946c2d88.tar.gz
[NEIGH] Print stack trace in neigh_add_timer
Stack traces are very helpful in determining the exact nature of a bug. So let's print a stack trace when the timer is added twice. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'net')
-rw-r--r--net/core/neighbour.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/net/core/neighbour.c b/net/core/neighbour.c
index 4128fc7..766caa0 100644
--- a/net/core/neighbour.c
+++ b/net/core/neighbour.c
@@ -732,6 +732,7 @@ static inline void neigh_add_timer(struct neighbour *n, unsigned long when)
if (unlikely(mod_timer(&n->timer, when))) {
printk("NEIGH: BUG, double timer add, state is %x\n",
n->nud_state);
+ dump_stack();
}
}
OpenPOWER on IntegriCloud