From owner-freebsd-current  Thu Apr 10 06:09:06 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id GAA04116
          for current-outgoing; Thu, 10 Apr 1997 06:09:06 -0700 (PDT)
Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA04107;
          Thu, 10 Apr 1997 06:09:00 -0700 (PDT)
Received: (from root@localhost) by dyson.iquest.net (8.8.4/8.6.9) id IAA00366; Thu, 10 Apr 1997 08:08:52 -0500 (EST)
From: "John S. Dyson" <toor@dyson.iquest.net>
Message-Id: <199704101308.IAA00366@dyson.iquest.net>
Subject: Re: NFS/mmap freeze in 2.2R
In-Reply-To: <199704100622.XAA19967@newport.ece.uci.edu> from Steven Wallace at "Apr 9, 97 11:22:15 pm"
To: swallace@ece.uci.edu (Steven Wallace)
Date: Thu, 10 Apr 1997 08:08:52 -0500 (EST)
Cc: bugs@freebsd.org, current@freebsd.org
Reply-To: dyson@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> 
> I have discovered how to freeze the system over an NFS mounted filesystem.
> If you map a file over NFS read/write and shared, write
> to the area in memory, and then have another program read that nfs file,
> the system will freeze.  The freeze is kindof wierd though.
> It appears that the kernel is still running somehow. 
> I can change the sysconts vty's but typing and all other processes
> are frozen and not running.
> 
Sounds like a recursive VFS locking problem or somesuch.  Thanks for the
report, and will look at it ASAP.

John