Subject: [PATCH] net: neighbour table ABI problem

From: Stephen Hemminger <[email-masked]>
Date: Wed, 21 May 2008 10:40:19 -0700

The neighbor table time of last use information is returned in the incorrect
unit. Kernel to user space ABI's need to use USER_HZ (or milliseconds), otherwise
the application has to try and discover the real system HZ value which is problematic.
Linux has standardized on keeping USER_HZ consistent (100hz) even when kernel is
running internally at some other value.

This change is small, but it breaks the ABI for older version of iproute2 utilities.
But these utilities are already broken since they are looking at the psched_hz values
which are completely different. So let's just go ahead and fix both kernel and user
space. Older utilities will just print wrong values.

Signed-off-by: Stephen Hemminger <[email-masked]>

--- a/net/core/neighbour.c	2008-05-21 10:23:05.000000000 -0700
+++ b/net/core/neighbour.c	2008-05-21 10:28:09.000000000 -0700
@@ -2057,9 +2057,9 @@ static int neigh_fill_info(struct sk_buf
 		goto nla_put_failure;
 	}
 
-	ci.ndm_used	 = now - neigh->used;
-	ci.ndm_confirmed = now - neigh->confirmed;
-	ci.ndm_updated	 = now - neigh->updated;
+	ci.ndm_used	 = jiffies_to_clock_t(now - neigh->used);
+	ci.ndm_confirmed = jiffies_to_clock_t(now - neigh->confirmed);
+	ci.ndm_updated	 = jiffies_to_clock_t(now - neigh->updated);
 	ci.ndm_refcnt	 = atomic_read(&neigh->refcnt) - 1;
 	read_unlock_bh(&neigh->lock);