From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <ee9e417a0809100741k4fa77e88o775f9bd7d3c4a1ec@mail.gmail.com>
Date: Wed, 10 Sep 2008 07:41:57 -0700
From: "Russ Cox" <rsc@swtch.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] Vacfs/9pfuse problems?
In-Reply-To: <140e7ec30809092125i30635834kedce2d37dda93061@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20080909134936.GB10171@meep>
	 <140e7ec30809092125i30635834kedce2d37dda93061@mail.gmail.com>
Topicbox-Message-UUID: 0e8bdacc-ead4-11e9-9d60-3106f5b1d025

There may be two bugs here.  One happens when you start 9pfuse in
one terminal and then interrupt a program in that same terminal.
Perhaps the shell sends the interrupt to the backgrounded 9pfuse
or 9p server too.  If so, there is an rfork(RFNOTEG) missing somewhere.

The second is what happens when any I/O to the 9pfuse server
gets interrupted, in any terminal.  That one:

>  I see the same 9pfuse behaviour mounting ircfs or u9fs at work. If I
> interrupt some I/O, I lose the mount.
>  Haven't seen the find problem, 9pfuse -D might be instructive there.

I think I fixed this on July 24.
http://hg.pdos.csail.mit.edu/hg/plan9/rev/18d28bd28f4b

Russ