From owner-freebsd-current Fri Apr 30 4: 8:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from ewok.creative.net.au (ewok.creative.net.au [203.30.44.41]) by hub.freebsd.org (Postfix) with SMTP id 2701814FB0 for ; Fri, 30 Apr 1999 04:08:24 -0700 (PDT) (envelope-from adrian@freebsd.org) Received: (qmail 14904 invoked by uid 1008); 30 Apr 1999 11:08:19 -0000 Message-ID: <19990430110819.14902.qmail@ewok.creative.net.au> From: adrian@freebsd.org To: Pierre Beyssac Cc: freebsd-current@freebsd.org Subject: Re: Any action on PR 10570 ? getting closer to 65K :-( In-reply-to: Your message of "Fri, 30 Apr 1999 12:26:51 +0200." <19990430122651.A11742@enst.fr> Date: Fri, 30 Apr 1999 19:08:18 +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pierre Beyssac writes: >On Fri, Apr 30, 1999 at 04:28:55PM +0800, adrian@FreeBSD.ORG wrote: >> I'll submit a followup to the pr, and a patch after I've verified it >> doesn't panic the system, but that will be sometime early next week >> (I can't setup a BGP connection to flood routes in and out before then..) > >Uh, from reading the PR it looks like it can be triggered by creating >a little more than 2^16 routes to the same destination, and then >deleting some of them to fall back under 2^16. I'm going to give >it a try now and I'll send you the script if that works. I'm also >making a world with "short" changed to "int" to see if it works. > >Wouldn't it be sensible to issue a warning (or panic) when increasing >the reference count reaches 0, rather than causing a later kernel >segfault? It would involve some overhead though, and I'm not sure >having 2^32 routes is currently realistic since most machines don't >even have that many bytes of RAM, but it might be true one day... >-- There isn't a reference to either IFAFREE or ifa_refcnt outside of /usr/src/sys on my tree. Adrian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message