From owner-freebsd-amd64@FreeBSD.ORG Mon May 17 14:31:04 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0420116A4CE; Mon, 17 May 2004 14:31:04 -0700 (PDT) Received: from daintree.corp.yahoo.com (daintree.corp.yahoo.com [216.145.52.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA1FA43D4C; Mon, 17 May 2004 14:31:03 -0700 (PDT) (envelope-from peter@yahoo-inc.com) Received: by daintree.corp.yahoo.com (Postfix, from userid 2154) id A64258826; Mon, 17 May 2004 14:31:03 -0700 (PDT) From: Peter Wemm To: freebsd-amd64@freebsd.org Date: Mon, 17 May 2004 14:31:03 -0700 User-Agent: KMail/1.6.1 References: <200405161836.17539.peter@wemm.org> In-Reply-To: <200405161836.17539.peter@wemm.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200405171431.03384.peter@wemm.org> cc: amd64@freebsd.org Subject: Re: Beware of dragons in module loader code! X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 May 2004 21:31:04 -0000 On Sunday 16 May 2004 06:36 pm, Peter Wemm wrote: > I've committed the support changes and enabled the new module loader, > but beware! It does still blow up! Consequently, I did *NOT* remove > the 'NO_MODULES' override in GENERIC etc because there are a number > of system daemons that will try and load things during startup. If > this suddenly started loading modules, it Would Be A Bad Thing. > > On an unrelated note, I could really use some eyes looking at the > sys/kern/link_elf_obj.c file. Somewhere, I have a bug (or a series > of bugs) that is causing significant memory trashing. Turns out that there were multiple bugs, some in my code (which I fixed as a side effect of something else), and the big one was in the kernel linker itself (not my bug! :-). Anyway, the guts of kldload(8) support is there now. Now for kldxref(8) and loader(8). Whee. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5