[PATCH 0/11] FUSE - Filesystem in Userspace

[Miklos Szeredi <miklos@xxxxxxxxxx>]

Andrew, Linus,

Please apply the following patches, which add Filesystem in Userspace
to the kernel.  The patches are against 2.6.10.

FUSE [1] exports the filesystem functionality to userspace.  The
communication interface is designed to be simple, efficient, secure
and able to support most of the usual filesystem semantics.

It can be used for prototyping and for network/virtual filesystems
requiring external libraries or programs.  A typical example is sshfs
[2] which uses the sftp protocol and allows zero-setup mounting of
remote sites.

FUSE is currently in use by dozens of publicly available filesystems
[3], and by many in-house applications.  It has proved useful and
stable for lots of users.

Thanks to everyone for the comments on the last submission.  Changes
since then are:

 - Made it Deadlock Free (TM).  This includes removing support for
   shared writable mapping and making all requests interruptible.

 - Removed INVALIDATE userspace initiated request, this is probably
   not used by any application.

 - Updated ABI to be independent of sizeof(long), so dual-size archs
   don't cause problems

 - Remove /sys/fs/fuse/version.  Version checking is now done through
   the fuse device

The patch is split up to the following parts:

  01 - MAINTAINERS, Kconfig and Makefile changes
  02 - FUSE core
  03 - FUSE device functions
  04 - read-only operations (getattr, readlink, readdir, ...)
  05 - read-write operations (setattr, mkdir, symlink, ...)
  06 - file operations (open, read, write, ...)
  07 - mount options controlling the behavior of the filesystem
  08 - extended attribute operations (getxattr, setxattr, ...)
  09 - readpages operation
  10 - NFS export support
  11 - direct I/O support

Thanks,
Miklos

[1] http://fuse.sourceforge.net/

[2] http://sourceforge.net/project/showfiles.php?group_id=121684&package_id=140425

[3] http://fuse.sourceforge.net/filesystems.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/