From owner-freebsd-current Sat Feb 16 10:32:42 2002 Delivered-To: freebsd-current@freebsd.org Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by hub.freebsd.org (Postfix) with ESMTP id 6533437B405 for ; Sat, 16 Feb 2002 10:32:37 -0800 (PST) Received: from laptop.6bone.nl (penguin.ripe.net [193.0.1.232]) by birch.ripe.net (8.11.6/8.11.6) with SMTP id g1GIWYa20020; Sat, 16 Feb 2002 19:32:34 +0100 Received: (nullmailer pid 29723 invoked by uid 1000); Sat, 16 Feb 2002 18:32:32 -0000 Date: Sat, 16 Feb 2002 19:32:32 +0100 From: Mark Santcroos To: Terry Lambert Cc: freebsd-current@FreeBSD.ORG Subject: Re: Ethernet tunnel device Message-ID: <20020216193232.B57907@laptop.6bone.nl> References: <20020211032336.A2135@kashmir.etowns.net> <20020211170131.A79104@laptop.6bone.nl> <20020212074327.A3466@laptop.6bone.nl> <20020213111358.A3235@kashmir.etowns.net> <20020213111937.A10146@Odin.AC.HMC.Edu> <3C6B0BFD.F27F040F@mindspring.com> <20020216004146.A57907@laptop.6bone.nl> <3C6DD38B.BF38EC80@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3C6DD38B.BF38EC80@mindspring.com>; from tlambert2@mindspring.com on Fri, Feb 15, 2002 at 07:35:39PM -0800 X-Handles: MS6-6BONE, MS18417-RIPE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Feb 15, 2002 at 07:35:39PM -0800, Terry Lambert wrote: > > > Maybe it's losing an open instance in the resource > > > track on close? That seems the most likely culprit... > > > > Do you mean in the linux emu case? > > If so, please see my message stating that I also used a linux emu program > > to test this. > > If not, can you please be a bit more detailed? > > Yes. > > I saw your message. It wasn't clear to me that you were > simply exiting in the test, instead of actually closing > the descriptor. I suspect that vmware just exits, and > expects a resource tracking close on exit to free the > reference count. If the Linux ABI code has not been > updated with all the necessary hand waving (old code was > OK, new code is broke ::= that's what's happening), then > that could easily cause the problem, whereas a test case > that does all the right manual shutdown would not have a > problem. Hi Terry, I did do an explicit close() in my test. However, using ktrace I also see a explicit close from vmware. That one doesn't reach the tap device however. So we are back to the original question, where does the close gets lost. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message