From owner-freebsd-current Fri Nov 6 12:34:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA27929 for freebsd-current-outgoing; Fri, 6 Nov 1998 12:34:57 -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 MAA27922 for ; Fri, 6 Nov 1998 12:34:53 -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 UAA28581; Fri, 6 Nov 1998 20:33:55 GMT Date: Fri, 6 Nov 1998 20:33:55 +0000 (GMT) From: Doug Rabson To: Andrzej Bialecki cc: freebsd-current@FreeBSD.ORG Subject: Re: nfs.ko panics on unloading In-Reply-To: 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, Andrzej Bialecki wrote: > Hi, > > With latest sources, running ELF kernel (and yes, I rebuilt kernel _and_ > modules) loading nfs.ko works ok, but unloading results in immediate panic > (page fault in kernel mode) and stack corruption. Is this a bug or a > feature? > > This is very repeatable here, but if anyone wants a coredump, I've got > one. There is a mistake in mount.h's module hooks for loading and initialising a filesystem. It calls vfs_register() at both load and unload time. I have some patches which I haven't got around to testing which disables unloading (and factor out some of the common vfs module registration code). Unfortunately the vfs system itself doesn't support unloading yet (a project for someone there). -- 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