From owner-freebsd-fs Fri Feb 26 9:22:39 1999 Delivered-To: freebsd-fs@freebsd.org Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20]) by hub.freebsd.org (Postfix) with ESMTP id BB6BA14CC6 for ; Fri, 26 Feb 1999 09:22:35 -0800 (PST) (envelope-from ezk@shekel.mcl.cs.columbia.edu) Received: from shekel.mcl.cs.columbia.edu (shekel.mcl.cs.columbia.edu [128.59.18.15]) by cs.columbia.edu (8.9.1/8.9.1) with ESMTP id MAA14495; Fri, 26 Feb 1999 12:22:06 -0500 (EST) Received: (from ezk@localhost) by shekel.mcl.cs.columbia.edu (8.9.1/8.9.1) id MAA02680; Fri, 26 Feb 1999 12:22:05 -0500 (EST) Date: Fri, 26 Feb 1999 12:22:05 -0500 (EST) Message-Id: <199902261722.MAA02680@shekel.mcl.cs.columbia.edu> X-Authentication-Warning: shekel.mcl.cs.columbia.edu: ezk set sender to ezk@shekel.mcl.cs.columbia.edu using -f From: Erez Zadok To: Steve McIntyre Cc: freebsd-fs@FreeBSD.ORG Subject: Re: KLD filesystems in 3.0? In-reply-to: Your message of "Fri, 26 Feb 1999 16:58:08 GMT." Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message , Steve McIntyre writes: [...] > I'm having some problems trying to write a filesystem (pfs) as a KLD. I > load the pfs module, and the startup code seems to work OK. I can mount > the filesystem, and still all seems OK. But the first time I try to do any > vnode ops in the FS all falls down - vn_stat tries to call pfsop_getattr > and fails, apparently trying to call a function at 0x0b instead of the > real address. My guess is that somehow the vnodeop entries are not being > registered properly; I've had a look through some of the other filesystems > and I can't see anything obvious that I'm missing. If this is by any chance a stackable f/s, then you might find the problem you're having by looking at my stackable template f/s (wrapfs) and several of the examples using wrapfs. http://www.cs.columbia.edu/~ezk/research/software/ Erez. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message