From owner-freebsd-current Sun Jul 9 16:31:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 9473937B90E for ; Sun, 9 Jul 2000 16:31:32 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id QAA25562; Sun, 9 Jul 2000 16:31:27 -0700 Date: Sun, 9 Jul 2000 16:31:28 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Ollivier Robert Cc: "FreeBSD Current Users' list" Subject: Re: Softupdates panic on SMP system In-Reply-To: <20000709123407.A27797@keltia.freenix.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I did some thinking about this, but no real code inspection, on a walk today- I think what is occurring is that the list of directory updates is getting refreshed from another process while the first process' list is being written out. A quick hack would be to make sure this doesn't happen (no -j4 for loose and gross and incomplete, some kind of worklist ownership token so that when process A wakes back up and looks at the worklist again it can see whether it still owns that list (after all, it drops the locks so it do the write). This is mostly a Kirk issue- he could say much quicker than I about this- I'd file this as a PR - I could fool around with it a little myself, but later this week. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message