From owner-freebsd-fs Sat Feb 27 15:34:37 1999 Delivered-To: freebsd-fs@freebsd.org Received: from assaris.sics.se (dyn02.trafford.dementia.org [204.29.154.130]) by hub.freebsd.org (Postfix) with ESMTP id E84E114C92 for ; Sat, 27 Feb 1999 15:34:33 -0800 (PST) (envelope-from assar@sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.1/8.7.3) id AAA34899; Sun, 28 Feb 1999 00:36:11 +0100 (CET) To: Steve McIntyre Cc: freebsd-fs@FreeBSD.ORG Subject: Re: KLD filesystems in 3.0? References: Mime-Version: 1.0 (generated by tm-edit 7.68) Content-Type: text/plain; charset=US-ASCII From: Assar Westerlund Date: 28 Feb 1999 00:36:10 +0100 In-Reply-To: Steve McIntyre's message of "Fri, 26 Feb 1999 16:58:08 +0000 (GMT)" Message-ID: <5lbtifh11x.fsf@mg.trafford.dementia.org> Lines: 15 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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. > > Does anybody out there have any ideas for things to check? Do you do an VNODEOP_SET on your `struct vnodeopv_desc'? /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message