From owner-freebsd-hackers Mon Feb 22 1:30: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id EA41810F58 for ; Mon, 22 Feb 1999 01:30:03 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA57532; Mon, 22 Feb 1999 09:28:42 GMT (envelope-from dfr@nlsystems.com) Date: Mon, 22 Feb 1999 09:28:42 +0000 (GMT) From: Doug Rabson To: Luoqi Chen Cc: mjacob@feral.com, freebsd-hackers@freebsd.org Subject: Re: Panic in FFS/4.0 as of yesterday - update In-Reply-To: <199902220442.XAA14152@lor.watermarkgroup.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 21 Feb 1999, Luoqi Chen wrote: > > > What troubled me here is why these supposedly async writes block (and ccd > > > is not involved)? I'd really like to see a dump of ps listing from ddb. > > > The async writes blocked on "nfsrcvlk". It looked like the test program > writeit was trying to clean some dirty nfs bufs. This situation shouldn't > be fatal as it is impossible to avoid blocking during async writes, getnewbuf > should simply return a NULL. The following patch should do the trick. Its certainly better than panicing but I'm still not happy about the recursion check (which is really just a reentrancy check since no recursion is actually happening). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message