From owner-freebsd-current Tue Apr 18 17:41:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id EE85437BA1C; Tue, 18 Apr 2000 17:41:31 -0700 (PDT) (envelope-from alc@cs.rice.edu) Received: (from alc@localhost) by cs.rice.edu (8.9.0/8.9.0) id TAA10012; Tue, 18 Apr 2000 19:41:27 -0500 (CDT) Date: Tue, 18 Apr 2000 19:41:26 -0500 From: Alan Cox To: Matthew Dillon Cc: Brian Fundakowski Feldman , Alfred Perlstein , Michael Reifenberger , current@freebsd.org, alc@freebsd.org Subject: Re: Anyone able to verify the fix for (was Re: panic: vm_object_shadow: source object has OBJ_ONEMAPPING set.) Message-ID: <20000418194126.C2616@cs.rice.edu> References: <200004181736.KAA14683@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5us In-Reply-To: <200004181736.KAA14683@apollo.backplane.com>; from Matthew Dillon on Tue, Apr 18, 2000 at 10:36:15AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This patch introduces a new bug. While it does guarantee that the assertion in vm_object_shadow isn't tripped over, it doesn't clear the OBJ_ONEMAPPING flag on the newly created shadow object. (New objects are created with OBJ_ONEMAPPING set.) Consequently, we'll have two overlapping mappings to the same shadow object that has OBJ_ONEMAPPING set. That's bad. The real problem is that the assertion is just plain wrong, not the code around it. It needs to be corrected or removed. Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message