Date: Sun, 8 Nov 1998 03:06:27 +1100 From: Bruce Evans <bde@zeta.org.au> To: dfr@nlsystems.com, wollman@khavrinen.lcs.mit.edu Cc: abial@nask.pl, freebsd-current@FreeBSD.ORG Subject: Re: nfs.ko panics on unloading Message-ID: <199811071606.DAA02999@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
>> > 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 I fixed most of the unloading problems in the NFS LKM before 3.0R. See nfs_uninit(). Most vfs's, including nfs, don't actually support unloading, because of bitrot in malloc() -- malloc_init() creates pointers that are left dangling after unload. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199811071606.DAA02999>