Skip site navigation (1)Skip section navigation (2)
Date:      18 Mar 2002 10:06:58 +0100
From:      Dag-Erling Smorgrav <des@ofug.org>
To:        Kris Kennaway <kris@obsecurity.org>
Cc:        Alfred Perlstein <alfred@freebsd.org>, current@freebsd.org, fs@freebsd.org
Subject:   Re: panic: bwrite: buffer is not busy???
Message-ID:  <xzp4rjep7m5.fsf@flood.ping.uio.no>
In-Reply-To: <20020318010245.A48956@xor.obsecurity.org>
References:  <20020317124958.A34008@xor.obsecurity.org> <xzpadt6r1xr.fsf@flood.ping.uio.no> <20020318061739.GB894@elvis.mu.org> <xzpvgbupdqa.fsf@flood.ping.uio.no> <20020318071623.GD894@elvis.mu.org> <20020318010245.A48956@xor.obsecurity.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway <kris@obsecurity.org> 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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzp4rjep7m5.fsf>