From owner-freebsd-current Fri Nov 6 13:02:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA02166 for freebsd-current-outgoing; Fri, 6 Nov 1998 13:02:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA02159 for ; Fri, 6 Nov 1998 13:02:48 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id VAA28704; Fri, 6 Nov 1998 21:01:39 GMT Date: Fri, 6 Nov 1998 21:01:39 +0000 (GMT) From: Doug Rabson To: Garrett Wollman cc: Andrzej Bialecki , freebsd-current@FreeBSD.ORG Subject: Re: nfs.ko panics on unloading In-Reply-To: <199811062039.PAA01859@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 6 Nov 1998, Garrett Wollman wrote: > < said: > > > code). Unfortunately the vfs system itself doesn't support unloading yet > > (a project for someone there). > > It certainly did before! NFS never did, no, because there was no way > to undefine a syscall, but when I first implemented VFS LKMs, you > definitely could unload them (provided that the reference count was > zero). I must be blind! I didn't even see vfs_unregister(). I'll tweak my patch and try to find time to test it. I think that NFS should define two modules, one for the vfs and one for the syscall (there isn't a predefined module type for syscalls yet though). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message