From owner-freebsd-current Fri Mar 22 21:48: 0 2002 Delivered-To: freebsd-current@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id 068C537B417; Fri, 22 Mar 2002 21:47:58 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id D1F43AE162; Fri, 22 Mar 2002 21:47:57 -0800 (PST) Date: Fri, 22 Mar 2002 21:47:57 -0800 From: Alfred Perlstein To: ak03@gte.com Cc: freebsd-current@FreeBSD.ORG, jroberson@chesapeake.net, arr@FreeBSD.ORG, obrien@FreeBSD.ORG Subject: Re: Found: module loading breakage Message-ID: <20020323054757.GQ10521@elvis.mu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.27i 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 * Alexander Kabaev [020322 21:31] wrote: > I used the workaround below to get the system booting again, but it > does nothing to solve the real problem. We should probably either update > each and every vnode known to the system with the new v_op pointer when > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message