[PATCH 2.5.68] mod_timer fix for dst.c

[PATCH 2.5.68] mod_timer fix for dst.c

[Vinay K Nallamothu]

[-- Attachment #1: Type: text/plain, Size: 91 bytes --]

Hi,

Small fix converting {del,add}_timer to mod_timer.

Applicable for 2.4.x also

vinay


[-- Attachment #2: dst.c.patch --]
[-- Type: text/plain, Size: 558 bytes --]

--- linux-2.5.68/net/core/dst.c	2003-03-25 10:08:35.000000000 +0530
+++ linux-2.5.68-mod/net/core/dst.c	2003-05-03 13:42:12.000000000 +0530
@@ -154,11 +154,9 @@
 	dst->next = dst_garbage_list;
 	dst_garbage_list = dst;
 	if (dst_gc_timer_inc > DST_GC_INC) {
-		del_timer(&dst_gc_timer);
 		dst_gc_timer_inc = DST_GC_INC;
 		dst_gc_timer_expires = DST_GC_MIN;
-		dst_gc_timer.expires = jiffies + dst_gc_timer_expires;
-		add_timer(&dst_gc_timer);
+		mod_timer(&dst_gc_timer, jiffies + dst_gc_timer_expires);
 	}
 	spin_unlock_bh(&dst_lock);
 }

Re: [PATCH 2.5.68] mod_timer fix for dst.c

[David S. Miller]

Post this to where it belongs, the linux-net and netdev
lists.

This is occuring far too frequently, and I'll be damned if I'm
going to be required to read each and every linux-kernel posting
to catch all of the networking patches.

Therefore, from now on I'm going to flat out ignore every
networking patch that is sent to lkml and isn't at least CC:'d to
linux-net, netdev, or the listed networking maintainers.  I mean
what the heck is the purpose of the MAINTAINERS entry if people
don't even use it?

-- 
David S. Miller <davem@redhat.com>