From owner-freebsd-current  Wed Apr  2 11:32:38 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA18289
          for current-outgoing; Wed, 2 Apr 1997 11:32:38 -0800 (PST)
Received: from critter.dk.tfs.com (phk.cybercity.dk [195.8.133.247])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA18260;
          Wed, 2 Apr 1997 11:31:59 -0800 (PST)
Received: from critter (localhost [127.0.0.1])
	by critter.dk.tfs.com (8.8.5/8.8.5) with ESMTP id VAA00249;
	Wed, 2 Apr 1997 21:30:52 +0200 (CEST)
To: Terry Lambert <terry@lambert.org>
cc: ache@nagual.ru (=?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?=), dyson@freebsd.org,
        bde@zeta.org.au, current@freebsd.org
Subject: Re: ufs lock panic in -current 
In-reply-to: Your message of "Wed, 02 Apr 1997 11:28:05 PDT."
             <199704021828.LAA14010@phaeton.artisoft.com> 
Date: Wed, 02 Apr 1997 21:30:51 +0200
Message-ID: <247.860009451@critter>
From: Poul-Henning Kamp <phk@critter.dk.tfs.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <199704021828.LAA14010@phaeton.artisoft.com>, Terry Lambert writes:

(Terry sent his standard reply #1:)
>
>The fix is conceptually non-trivial, and requires that the transitive
>closure be calculated at the same layer for all FS's.  This implies a
>veto, rather than a call-down, interface for VOP_LOCK.
>
>Physically, the fix is about 200 lines of code, including all FS
>code changes.

(And I send my standard reply #1:)

Well, send us the patch Terry!

--
Poul-Henning Kamp           | phk@FreeBSD.ORG       FreeBSD Core-team.
http://www.freebsd.org/~phk | phk@login.dknet.dk    Private mailbox.
whois: [PHK]                | phk@tfs.com           TRW Financial Systems, Inc.
Power and ignorance is a disgusting cocktail.