From owner-freebsd-current Fri Aug 20 22:33:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 6725D14D11 for ; Fri, 20 Aug 1999 22:33:29 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id HAA11058; Sat, 21 Aug 1999 07:30:46 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: John Birrell Cc: Luigi Rizzo , Andrew Atrens , current@FreeBSD.ORG Subject: Re: problem with vnconfig -s labels ... In-reply-to: Your message of "Sat, 21 Aug 1999 15:11:41 +1000." <19990821151141.A281@freebsd1.cimlogic.com.au> Date: Sat, 21 Aug 1999 07:30:46 +0200 Message-ID: <11056.935213446@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990821151141.A281@freebsd1.cimlogic.com.au>, John Birrell writes: >The problem is that disklabel executes code in subr_diskslice.c which >does: > >dev1 = dkmodslice(dkmodpart(dev, RAW_PART), slice); > >The 'dev' structure has s_drv1 set correctly, but the 'dev1' entry >has s_drv1 NULL. When vnstrategy() is called using dev1, >vn = bp->b_dev->s_drv1 is NULL when it shouldn't be. The first time >vn is referenced... fall down go boom. Bingo, thats it. >but I'm still looking for the place >where the dev1 entry is supposed to be initialised. In dkmodslice() (and friends). -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message