From owner-freebsd-current Fri Mar 22 22: 1:25 2002 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id C94B137B41B; Fri, 22 Mar 2002 22:01:21 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g2N61Km66589; Fri, 22 Mar 2002 22:01:20 -0800 (PST) (envelope-from dillon) Date: Fri, 22 Mar 2002 22:01:20 -0800 (PST) From: Matthew Dillon Message-Id: <200203230601.g2N61Km66589@apollo.backplane.com> To: Alfred Perlstein Cc: ak03@gte.com, freebsd-current@FreeBSD.ORG, jroberson@chesapeake.net, arr@FreeBSD.ORG, obrien@FreeBSD.ORG Subject: Re: Found: module loading breakage References: <20020323054757.GQ10521@elvis.mu.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :> needed, or simply start allocating vop_t vectors large enough to hold :> every vnode operation we know about. Or maybe some VFS guru can :> propose a better strategy? : :Good work! : :I was about to say: : "why don't you just traverse the system wide list of vnodes : and fixup the pointers?" :Then I realized that there doesn't seem to be a system wide list... :( : :You could add one, it would be trivial to add a TAILQ_ENTRY to the :vnode strcture as well as add/remove the nodes from :the list in the vnode allocation and deallocation code. : :Feel ambitious? :) : :-Alfred Unless I am missing something, vnodes hang off their mount points. So, effectively, there is a system-wide list. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message