Date: Sat, 15 Apr 2000 20:18:01 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: Alfred Perlstein <bright@wintelcom.net> Cc: Brian Fundakowski Feldman <green@FreeBSD.ORG>, Michael Reifenberger <root@nihil.plaut.de>, FreeBSD-Current <current@FreeBSD.ORG>, alc@FreeBSD.ORG Subject: Re: panic: vm_object_shadow: source object has OBJ_ONEMAPPING set. Message-ID: <200004160318.UAA82192@apollo.backplane.com> References: <Pine.BSF.4.21.0004150932460.16247-100000@green.dyndns.org> <200004151803.LAA79656@apollo.backplane.com> <20000415123212.S4381@fw.wintelcom.net>
next in thread | previous in thread | raw e-mail | index | archive | help
:Is there a good reason for not having the vm_object_clear_flag() in
:vm_object_reference()?
Well, yes... vm_object's are referenced for all sorts of things
temporarily. Everything from a process looking one up temporarily
to the swap code issuing I/O. None of these references have anything
to do with OBJ_ONEMAPPING.
:A reference count leak did occur, ref_count was bumped without other
:sanity flags being cleared, the code makes it easy to shoot yourself
:in the foot.
This is not necessarily a leak. If you have discontinuous vm_map_entry
structures pointing to the same vm_object, then the vm_object will have
a big reference count and can still be set OBJ_ONEMAPPING.
-Matt
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?200004160318.UAA82192>