From owner-freebsd-hackers Tue Feb 17 14:47:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA08518 for freebsd-hackers-outgoing; Tue, 17 Feb 1998 14:47:53 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA08409 for ; Tue, 17 Feb 1998 14:47:15 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id PAA12448; Tue, 17 Feb 1998 15:42:52 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp03.primenet.com, id smtpd012371; Tue Feb 17 15:42:44 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id PAA04920; Tue, 17 Feb 1998 15:42:32 -0700 (MST) From: Terry Lambert Message-Id: <199802172242.PAA04920@usr09.primenet.com> Subject: Re: VM messed: vm_page_free panic problem To: michaelh@cet.co.jp (Michael Hancock) Date: Tue, 17 Feb 1998 22:42:31 +0000 (GMT) Cc: Tor.Egge@idi.ntnu.no, mike@smith.net.au, toor@dyson.iquest.net, hackers@FreeBSD.ORG In-Reply-To: from "Michael Hancock" at Feb 17, 98 11:19:50 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Somehow, this still seems to be a work-around to me. We shouldn't panic > because mfs doesn't implement VOP_GETPAGES. Unfortunately, I can't think > of a fix that isn't ugly. VOP_FINALVP would fix this. Barring that, all local media FS's *must* implement the interfaces VOP_GETPAGES/VOP_PUTPAGES. If all local media FS's implemented this, then all other FS's could use non-definition of a default decsriptor. This would make stacked FS's properly use the "bypass" mechanism to get to the correct underlying physical media FS's VOP_GETPAGES/VOP_PUTPAGES. Using the "bypass" mechanism is the correct way to deal with this. It's also the correct way to deal with the synchronization crap that was jammed into the nullfs, making it non-NULL. The alias object vs. object alias changes John made only partially mask some of these problems. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message