From owner-freebsd-current Sat Apr 15 20:18: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 5575737B933; Sat, 15 Apr 2000 20:18:02 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA82192; Sat, 15 Apr 2000 20:18:01 -0700 (PDT) (envelope-from dillon) Date: Sat, 15 Apr 2000 20:18:01 -0700 (PDT) From: Matthew Dillon Message-Id: <200004160318.UAA82192@apollo.backplane.com> To: Alfred Perlstein Cc: Brian Fundakowski Feldman , Michael Reifenberger , FreeBSD-Current , alc@FreeBSD.ORG Subject: Re: panic: vm_object_shadow: source object has OBJ_ONEMAPPING set. References: <200004151803.LAA79656@apollo.backplane.com> <20000415123212.S4381@fw.wintelcom.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :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