diff options
author | Herbert Xu <herbert@gondor.apana.org.au> | 2005-10-23 02:11:39 -0400 |
---|---|---|
committer | Herbert Xu <herbert@gondor.apana.org.au> | 2005-10-23 02:11:39 -0400 |
commit | 203755029e063066ecc4cf5eee1110ab946c2d88 (patch) | |
tree | 2f57df251c75847c7fe6e5c694319553733812b9 | |
parent | d475f3f47a0427dfee483cecf9a7e9109e991423 (diff) |
[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>
-rw-r--r-- | net/core/neighbour.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/net/core/neighbour.c b/net/core/neighbour.c index 4128fc76ac3a..766caa0dd930 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) | |||
732 | if (unlikely(mod_timer(&n->timer, when))) { | 732 | if (unlikely(mod_timer(&n->timer, when))) { |
733 | printk("NEIGH: BUG, double timer add, state is %x\n", | 733 | printk("NEIGH: BUG, double timer add, state is %x\n", |
734 | n->nud_state); | 734 | n->nud_state); |
735 | dump_stack(); | ||
735 | } | 736 | } |
736 | } | 737 | } |
737 | 738 | ||