From owner-freebsd-current Mon Jun 28 1:37: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id A0F4414CC0 for ; Mon, 28 Jun 1999 01:36:36 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id B54E582; Mon, 28 Jun 1999 16:36:31 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Kirk McKusick Cc: Matthew Dillon , Alan Cox , Julian Elischer , Mike Smith , "John S. Dyson" , dg@root.com, dyson@iquest.net, current@freebsd.org, Greg Lehey Subject: Re: Found the startup panic - ccd ( patch included ) In-reply-to: Your message of "Sun, 27 Jun 1999 20:47:51 MST." <199906280347.UAA01061@flamingo.McKusick.COM> Date: Mon, 28 Jun 1999 16:36:31 +0800 From: Peter Wemm Message-Id: <19990628083631.B54E582@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kirk McKusick wrote: [..] Re: kern_lock.c - looks like a reasonable fix. There isn't much point panicing for a poll. > I do not see the problem that you are pointing out with missing > BUF_KERNPROC in cluster_callback, but it is well past midnight, > so I may not be thinking clearly. No, you are correct. I had experimented with moving the cluster_head reassignment to LK_KERNPROC out of BUF_KERNPROC() and into the point where it was added into the tailq, but in the end I realized it wasn't much different and suspected that there could be problems if the cluster build was abandoned at some point, so I left it the way it is. > Greg Lehey has sent me a panic with the buffer locking in the NFS code. > I am too tired to attack it tonight, but will look at it in the morning. I might have a look if I get a chance.. > Kirk Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message