summaryrefslogtreecommitdiffstats
path: root/Documentation
diff options
context:
space:
mode:
authorDenis Lunev <den@sw.ru>2005-07-30 17:47:25 -0700
committerDavid S. Miller <davem@davemloft.net>2005-07-30 17:47:25 -0700
commitf0098f7863f814a5adc0b9cb271605d063cad7fa (patch)
tree7477022770edd99422586372147e9b0f48de4c63 /Documentation
parentdb44575f6fd55df6ff67ddd21f7ad5be5a741136 (diff)
[NET] Fix too aggressive backoff in dst garbage collection
The bug is evident when it is seen once. dst gc timer was backed off, when gc queue is not empty. But this means that timer quickly backs off, if at least one destination remains in use. Normally, the bug is invisible, because adding new dst entry to queue cancels the backoff. But it shots deadly with destination cache overflow when new destinations are not released for long time f.e. after an interface goes down. The fix is to cancel backoff when something was released. Signed-off-by: Denis Lunev <den@sw.ru> Signed-off-by: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions