Bug 135502 - [periodic] Warning message raised by rtfree function in kernel logs
Summary: [periodic] Warning message raised by rtfree function in kernel logs
Status: Closed Overcome By Events
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 7.2-RELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-12 13:10 UTC by Olivier BONHOMME
Modified: 2018-02-18 07:50 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Olivier BONHOMME 2009-06-12 13:10:01 UTC 
In a quite randomly way, the following message appears in the kernel logs : 

Jun  3 03:13:52 ares kernel: rtfree: 0xffffff00690753e0 has 2 refs.

This message seems to be enhanced always by the same task because it appears always at the same hour but not every day.

This server has several IPv4 and IPv6 addresses.

Could this behavior be linked to this thread : 

http://lists.freebsd.org/pipermail/freebsd-net/2007-August/015153.html

I checked the source code and the rtfree function in stead of RTFREE_LOCKED version is called.

Fix: 

Maybe replacing rtfree by RTFREE_LOCKED as told in the ML thread.
How-To-Repeat: Random behavior => Not easily reproductible
Comment 1 Volker Werth freebsd_committer freebsd_triage 2009-06-16 22:26:38 UTC 
Responsible Changed
From-To: freebsd-bugs->freebsd-net


Over to maintainer(s). 
This may happen for gif tunnels and v6 interfaces as cscope  
suggests there're direct calls to rtfree() from  
in6_gif.c, in6_ifattach.c and nd6_nbr.c
Comment 2 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 08:00:32 UTC 
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped
Comment 3 Alex Kozlov freebsd_committer freebsd_triage 2018-02-18 07:50:41 UTC 
Solution suggested in this bug report is no longer applicable due to major changes in the source code.