From owner-freebsd-fs Mon Mar 18 1: 7: 4 2002 Delivered-To: freebsd-fs@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id B79C437B400; Mon, 18 Mar 2002 01:07:00 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 3F1585347; Mon, 18 Mar 2002 10:06:59 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Kris Kennaway Cc: Alfred Perlstein , current@freebsd.org, fs@freebsd.org Subject: Re: panic: bwrite: buffer is not busy??? References: <20020317124958.A34008@xor.obsecurity.org> <20020318061739.GB894@elvis.mu.org> <20020318071623.GD894@elvis.mu.org> <20020318010245.A48956@xor.obsecurity.org> From: Dag-Erling Smorgrav Date: 18 Mar 2002 10:06:58 +0100 In-Reply-To: <20020318010245.A48956@xor.obsecurity.org> Message-ID: Lines: 13 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Kris Kennaway writes: > With the corrected version of that patch (and a patch from Tor to fix > VM deadlocks in green's commit) I got this panic. ...which is completely uninteresting, actually, except as proof that the patch (and my initial analysis) is incorrect. With the patch applied, tail(1) will *always* cause this panic; it is a direct and inevitable consequence of the patch clearing p->p_fd before calling closef(). DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message