android_kernel_motorola_sm6225/fs/fuse
Miklos Szeredi 79c0b2df79 add filesystem subtype support
There's a slight problem with filesystem type representation in fuse
based filesystems.

From the kernel's view, there are just two filesystem types: fuse and
fuseblk.  From the user's view there are lots of different filesystem
types.  The user is not even much concerned if the filesystem is fuse based
or not.  So there's a conflict of interest in how this should be
represented in fstab, mtab and /proc/mounts.

The current scheme is to encode the real filesystem type in the mount
source.  So an sshfs mount looks like this:

  sshfs#user@server:/   /mnt/server    fuse   rw,nosuid,nodev,...

This url-ish syntax works OK for sshfs and similar filesystems.  However
for block device based filesystems (ntfs-3g, zfs) it doesn't work, since
the kernel expects the mount source to be a real device name.

A possibly better scheme would be to encode the real type in the type
field as "type.subtype".  So fuse mounts would look like this:

  /dev/hda1       /mnt/windows   fuseblk.ntfs-3g   rw,...
  user@server:/   /mnt/server    fuse.sshfs        rw,nosuid,nodev,...

This patch adds the necessary code to the kernel so that this can be
correctly displayed in /proc/mounts.

Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-05-08 11:15:01 -07:00
..
control.c [PATCH] mark struct inode_operations const 1 2007-02-12 09:48:46 -08:00
dev.c [PATCH] slab: remove kmem_cache_t 2006-12-07 08:39:25 -08:00
dir.c [PATCH] fuse: validate rootmode mount option 2007-04-08 19:47:55 -07:00
file.c locks: give posix_test_lock same interface as ->lock 2007-05-06 17:39:00 -04:00
fuse_i.h [PATCH] fuse: validate rootmode mount option 2007-04-08 19:47:55 -07:00
inode.c add filesystem subtype support 2007-05-08 11:15:01 -07:00
Makefile [PATCH] fuse: add control filesystem 2006-06-25 10:01:19 -07:00