From f0098f7863f814a5adc0b9cb271605d063cad7fa Mon Sep 17 00:00:00 2001
From: Denis Lunev <den@sw.ru>
Date: Sat, 30 Jul 2005 17:47:25 -0700
Subject: [PATCH] [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>
---
Reading git-format-patch failed