Date: Fri, 15 Feb 2002 19:35:39 -0800 From: Terry Lambert <tlambert2@mindspring.com> To: Mark Santcroos <marks@ripe.net> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Ethernet tunnel device Message-ID: <3C6DD38B.BF38EC80@mindspring.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
Mark Santcroos wrote: > On Wed, Feb 13, 2002 at 04:59:41PM -0800, Terry Lambert wrote: > > > There's one difference between vmware and a little hacked up test app. > > > Linux emulation. It certaintly shouldn't matter, but it might be worth > > > compiling the test program on a linux machine and seeing it it leaves > > > the device in a weird state like vmware. > > > > 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. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3C6DD38B.BF38EC80>