Fuse panics when accessing a file that does not show up with 'ls'

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create a process, mutex, or channel
2. Attempt to cat or write to a file that is not yet there (e.g., stdin)
3. Hang. Note that there is a panic displayed on the circuit terminal

What is the expected output? What do you see instead?

The system should act as though those files do not exist, and it mostly does. 
When a reflected endpoint, like Stdin() or Write() returns nil, the file is not 
listed when the directory is read. But the file is still "there" in a sense. If 
you try to access it, e.g., via Walk or Open, that is still attempted by fuse 
and you get a panic. There needs to be some short-circuiting logic in there to 
special-case nil endpoints in all situations.

Original issue reported on code.google.com by ch...@gocircuit.org on 11 Feb 2014 at 1:39

[GoogleCodeExporter]

Wrong tracker link. Sorry about that.

Original comment by ch...@gocircuit.org on 11 Feb 2014 at 1:42

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

You should look at code.google.com/p/swarming/ :P

Original comment by maruel@chromium.org on 11 Feb 2014 at 1:49

• Changed state: Invalid
• Added labels: ****
• Removed labels: ****