Re: rtfree: 0xc3e377f8 has 1 refs

Basically, this looks like a side effect of calling rtfree() on a route
when we dont hold the last reference.  In reality we should be using the
RTFREE()/REFREE_LOCKED() helper macros which manage reference counts
in this case.

I have attached a patch, please let me know if this helps. BTW, nice
hostname :)

On Sun, Sep 02, 2007 at 02:05:34AM +0100, Hugo wrote:
> Hi list,
> 
> While experimenting with IPv6 on a spare server, I noticed the following in 
> the logs:
> 
> Sep  2 00:24:33 deserteagle kernel: rtfree: 0xc3e377f8 has 1 refs
> Sep  2 00:25:01 deserteagle last message repeated 139 times
> Sep  2 00:25:01 deserteagle kernel: rtfree: 0xc3e377f8 has 1 refs
> Sep  2 00:25:17 deserteagle last message repeated 401 times
> Sep  2 00:27:38 deserteagle last message repeated 1204 times
> Sep  2 00:35:32 deserteagle last message repeated 1032 times
> Sep  2 00:47:03 deserteagle last message repeated 164 times
> 
> 
> Connectivity is fine, but these messages are filling up the logs. The only 
> traffic that particular server gets right now is ssh (over ipv6, altough by 
> looking at the logs the messages show up even before I login)
> 
> 
> uname:
> 7.0-CURRENT FreeBSD 7.0-CURRENT #2: Sat Sep  1 23:07:18 UTC 2007     
> klr_at_deserteagle.barafranca.com:/usr/obj/usr/src/sys/DESERTEAGLE  i386
> 
> 
> netstat -rn:
> Internet6:
> Destination                       Gateway                       Flags      
> Netif Expire
> ::/96                             ::1                           UGRS        
> lo0 =>
> default                           2002:c058:6301::              UGS        
> stf0
> ::1                               ::1                           UHL         
> lo0
> ::ffff:0.0.0.0/96                 ::1                           UGRS        
> lo0
> 2002::/24                         ::1                           UGRS        
> lo0 =>
> 2002::/16                         2002:4655:c4f2::1             U          
> stf0
> 2002:4655:c4f2::/48               link#1                        UC          
> em0
> 2002:4655:c4f2::1                 link#4                        UHL         
> lo0
> 2002:4655:c4f2::ac1d:242          00:0c:f1:bf:2a:54             UHL         
> lo0
> 2002:4655:c4f2::ac1d:243          00:0c:f1:bf:2a:54             UHL         
> lo0
> 2002:7f00::/24                    ::1                           UGRS        
> lo0
> 2002:e000::/20                    ::1                           UGRS        
> lo0
> 2002:ff00::/24                    ::1                           UGRS        
> lo0
> fe80::/10                         ::1                           UGRS        
> lo0
> fe80::%em0/64                     link#1                        UC          
> em0
> fe80::20c:f1ff:febf:2a54%em0      00:0c:f1:bf:2a:54             UHL         
> lo0
> fe80::%lo0/64                     fe80::1%lo0                   U           
> lo0
> fe80::1%lo0                       link#3                        UHL         
> lo0
> ff01:1::/32                       link#1                        UC          
> em0
> ff01:3::/32                       ::1                           UC          
> lo0
> ff02::/16                         ::1                           UGRS        
> lo0
> ff02::%em0/32                     link#1                        UC          
> em0
> ff02::%lo0/32                     ::1                           UC          
> lo0
> 
> 
> 
> I have never seen this error before. On a 6.2-RELEASE-p1 box at home (which 
> also got ipv6 connectivity) I do not see these errors.
> 
> Ideas?
> 
> Best regards,
> 
> Hugo
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"

-- 
Christian S.J. Peron
csjp_at_FreeBSD.ORG
FreeBSD Committer