From owner-freebsd-current Tue Jul 4 4:55:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from mimer.webgiro.com (mimer.webgiro.com [212.209.29.5]) by hub.freebsd.org (Postfix) with ESMTP id D340237B7EE for ; Tue, 4 Jul 2000 04:55:14 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by mimer.webgiro.com (Postfix, from userid 66) id A207F2DC0A; Tue, 4 Jul 2000 14:00:55 +0200 (CEST) Received: by mx.webgiro.com (Postfix, from userid 1001) id 1CE0C7817; Tue, 4 Jul 2000 13:50:53 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id 1646C10E17; Tue, 4 Jul 2000 13:50:53 +0200 (CEST) Date: Tue, 4 Jul 2000 13:50:51 +0200 (CEST) From: Andrzej Bialecki To: Kelly Yancey Cc: freebsd-current@FreeBSD.ORG Subject: Re: Possible bug in netinet6/in6_rmx.c ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 2 Jul 2000, Kelly Yancey wrote: > On Sun, 2 Jul 2000, Andrzej Bialecki wrote: > > > Hi, > > > > While working on adding dynamic sysctls support, I discovered something > > that looks like a bug. > > > > For kernels that have both INET and INET6, three sysctl entries (rtexpire, > > rtminexpire, rtmaxcache) are registered twice - both in netinet/in_rmx.c > > and netinet6/in6_rmx.c. > > > > It seems they should be registered only once, within a section that is > > common to INET and INET6. > > > > Andrzej Bialecki > > > > I think the real problem is that the rtexpire, rtminexpire, and rtmaxcache > variables are each declared static in netinet/in_rmx.c and again in > netinet6/in6_in6_rmx.c. Do we really need separate learned route expiration > times for ip4 and ip6? If the answer is yes, then the solution should be to > move the ip6 versions under the net.inet.ip6 sysctl tree. > Otherwise, as you suggest, rtexpire and friends need to be common (maybe > directly under net.inet?) Yeah, something like that. The question is who is going to fix it? INET6 issues should probably stay in sync with other BSDs and KAME, and therefore IMHO the maintainer of inet6 code should step out and fix it... (Hello?? :) > By the way, while we are talking about sysctl, I don't suppose you would be > willing to review/commit PR 15251? It is a fairly straightforward patch that I see Jonathan Bresler took it (today). Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message