This avoids involving the go 1.9 poller in I/O, which causes hangs, as
the poller does not understand the fcntl(O_NONBLOCK) tweak that we
executed on the pipe's file descriptors.

Fixes #164

The root user can issue the umount syscall and does not need the
fusermount binary. Therefore, it is not necessary to fork and exec a new
process just to run the umount binary.

Golang has a global lock held for forking (See exec_unix.go in the golang
source tree):
"Acquire the fork lock so that no other threads create new fds that are
not yet close-on-exec before we fork."

So it would be best if processes would refrain from forking
unnecessarily.
Signed-off-by: Shayan Pooya <shayan@arista.com>

This fixes 'du'.

Fixes #159.

Fixes #160.

This first race was easy to find and fix in the tests themselves.

It exposes another race in nodefs.FileSystemConnector where a node's
mount (and therefore, treeLock) is is not the same as the grand-parent
node's is.

Updates #138.

Fixes #134

Change-Id: I04eb8c16d45dbeef872036aab4091741b981505c

Fixes #127.

This enhances nodes which embed defaultNode (which is most of them),
allowing those implementations to omit a GetAttr() method. Without this,
when the kernel calls GetAttr() for an open file, FUSE will return a
size of zero, causing a read() of the file to always return 0, even
though fuse returns a nonzero number of bytes.

One can leverage this behavior to create a Linux procfs-like file, which
stat shows to be zero bytes, but can be successfully read.

N.B. This behavior is only useful if the FileSystemConnector Options
specify AttrTimeout of zero. Otherwise, the result of the first call to
GetAttr() (file == nil) is cached, and the kernel allows zero bytes to
be read. With this caching disabled, the next GetAttr() call (file !=
nil) will be used to control the number of readable bytes.

1) Fix the "a" instead of "m" typo in loopbackFile.Utimens.
   Besides the incorrect behavoir, this causes a crash if "a"
   is nil.
   Obsoletes https://github.com/hanwen/go-fuse/pull/100 .

2) Enable nanosecond resolution for dates after 1970.
   syscall.NsecToTimespec is broken for dates before 1970 but
   works fine otherwise, so let's keep the nanoseconds there.

3) Deduplicate the time conversion code in nodefs and paths into
   the new function fuse.UtimeToTimespec.

4) Add a test case.

Panic if we insert invalid branchResult into the cache.

Should provide more data for bug #109.

Ensure all.bash tests compilation on both Darwin and Linux.

Fixes #125.

This makes it evident which tests leak mount points.

Move shared test utilities into internal/testutil/ package.

This is less overhead, and fixes the darwin tests that use InitIn.

Fixed handling of ENOSYS in unionfs.

When mounting using relative paths, "touch" on directories
used to fail.

"touch" on files works accidentially because it uses a
file descriptor internally.

  $ loopback b a &
  $ cd b
  $ mkdir foo
  $ touch foo
  touch: setting times of 'foo': Not a directory

strace:

  [pid 30185] utimensat(0, "a/foo", [{1468441847, 0}, {1468441847, 0}], AT_SYMLINK_NOFOLLOW <unfinished ...>
  [pid 30185] <... utimensat resumed> )   = -1 ENOTDIR (Not a directory)

On Mac OS X the Finder loses its mind if GetXAttr returns ENODATA
rather than ENOATTR. On Linux, ENOATTR is just an alias for ENOATTR.

The Linux man page references ENOATTR:
http://man7.org/linux/man-pages/man2/fgetxattr.2.html

Gerrithub requires overly broad write permissions, and hence its usage
is discontinued.

Add AUTHORS file.

This makes CFuse and go-fuse easier to compare.  Get rid of the
baroque analysis code, unused delay code, and some general cleanup.

Surpress benchmark if -v is not given.

circuit our read.

Change-Id: Id83c4b3738c5cedf9d9b738cab21632db6061126