2005-04-17 02:20:36 +04:00
/*
* linux / fs / filesystems . c
*
* Copyright ( C ) 1991 , 1992 Linus Torvalds
*
* table of configured filesystems
*/
# include <linux/syscalls.h>
# include <linux/fs.h>
2008-10-04 14:08:37 +04:00
# include <linux/proc_fs.h>
# include <linux/seq_file.h>
2005-04-17 02:20:36 +04:00
# include <linux/slab.h>
# include <linux/kmod.h>
# include <linux/init.h>
# include <linux/module.h>
# include <asm/uaccess.h>
/*
* Handling of filesystem drivers list .
* Rules :
* Inclusion to / removals from / scanning of list are protected by spinlock .
* During the unload module must call unregister_filesystem ( ) .
* We can access the fields of list element if :
* 1 ) spinlock is held or
* 2 ) we hold the reference to the module .
* The latter can be guaranteed by call of try_module_get ( ) ; if it
* returned 0 we must skip the element , otherwise we got the reference .
* Once the reference is obtained we can drop the spinlock .
*/
static struct file_system_type * file_systems ;
static DEFINE_RWLOCK ( file_systems_lock ) ;
/* WARNING: This can be used only if we _already_ own a reference */
void get_filesystem ( struct file_system_type * fs )
{
__module_get ( fs - > owner ) ;
}
void put_filesystem ( struct file_system_type * fs )
{
module_put ( fs - > owner ) ;
}
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:25:43 +04:00
static struct file_system_type * * find_filesystem ( const char * name , unsigned len )
2005-04-17 02:20:36 +04:00
{
struct file_system_type * * p ;
for ( p = & file_systems ; * p ; p = & ( * p ) - > next )
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:25:43 +04:00
if ( strlen ( ( * p ) - > name ) = = len & &
strncmp ( ( * p ) - > name , name , len ) = = 0 )
2005-04-17 02:20:36 +04:00
break ;
return p ;
}
/**
* register_filesystem - register a new filesystem
* @ fs : the file system structure
*
* Adds the file system passed to the list of file systems the kernel
* is aware of for mount and other syscalls . Returns 0 on success ,
* or a negative errno code on an error .
*
* The & struct file_system_type that is passed is linked into the kernel
* structures and must not be freed until the file system has been
* unregistered .
*/
int register_filesystem ( struct file_system_type * fs )
{
int res = 0 ;
struct file_system_type * * p ;
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:25:43 +04:00
BUG_ON ( strchr ( fs - > name , ' . ' ) ) ;
2005-04-17 02:20:36 +04:00
if ( fs - > next )
return - EBUSY ;
INIT_LIST_HEAD ( & fs - > fs_supers ) ;
write_lock ( & file_systems_lock ) ;
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:25:43 +04:00
p = find_filesystem ( fs - > name , strlen ( fs - > name ) ) ;
2005-04-17 02:20:36 +04:00
if ( * p )
res = - EBUSY ;
else
* p = fs ;
write_unlock ( & file_systems_lock ) ;
return res ;
}
EXPORT_SYMBOL ( register_filesystem ) ;
/**
* unregister_filesystem - unregister a file system
* @ fs : filesystem to unregister
*
* Remove a file system that was previously successfully registered
* with the kernel . An error is returned if the file system is not found .
* Zero is returned on a success .
*
* Once this function has returned the & struct file_system_type structure
* may be freed or reused .
*/
int unregister_filesystem ( struct file_system_type * fs )
{
struct file_system_type * * tmp ;
write_lock ( & file_systems_lock ) ;
tmp = & file_systems ;
while ( * tmp ) {
if ( fs = = * tmp ) {
* tmp = fs - > next ;
fs - > next = NULL ;
write_unlock ( & file_systems_lock ) ;
return 0 ;
}
tmp = & ( * tmp ) - > next ;
}
write_unlock ( & file_systems_lock ) ;
return - EINVAL ;
}
EXPORT_SYMBOL ( unregister_filesystem ) ;
static int fs_index ( const char __user * __name )
{
struct file_system_type * tmp ;
char * name ;
int err , index ;
name = getname ( __name ) ;
err = PTR_ERR ( name ) ;
if ( IS_ERR ( name ) )
return err ;
err = - EINVAL ;
read_lock ( & file_systems_lock ) ;
for ( tmp = file_systems , index = 0 ; tmp ; tmp = tmp - > next , index + + ) {
if ( strcmp ( tmp - > name , name ) = = 0 ) {
err = index ;
break ;
}
}
read_unlock ( & file_systems_lock ) ;
putname ( name ) ;
return err ;
}
static int fs_name ( unsigned int index , char __user * buf )
{
struct file_system_type * tmp ;
int len , res ;
read_lock ( & file_systems_lock ) ;
for ( tmp = file_systems ; tmp ; tmp = tmp - > next , index - - )
if ( index < = 0 & & try_module_get ( tmp - > owner ) )
break ;
read_unlock ( & file_systems_lock ) ;
if ( ! tmp )
return - EINVAL ;
/* OK, we got the reference, so we can safely block */
len = strlen ( tmp - > name ) + 1 ;
res = copy_to_user ( buf , tmp - > name , len ) ? - EFAULT : 0 ;
put_filesystem ( tmp ) ;
return res ;
}
static int fs_maxindex ( void )
{
struct file_system_type * tmp ;
int index ;
read_lock ( & file_systems_lock ) ;
for ( tmp = file_systems , index = 0 ; tmp ; tmp = tmp - > next , index + + )
;
read_unlock ( & file_systems_lock ) ;
return index ;
}
/*
* Whee . . Weird sysv syscall .
*/
2009-01-14 16:14:29 +03:00
SYSCALL_DEFINE3 ( sysfs , int , option , unsigned long , arg1 , unsigned long , arg2 )
2005-04-17 02:20:36 +04:00
{
int retval = - EINVAL ;
switch ( option ) {
case 1 :
retval = fs_index ( ( const char __user * ) arg1 ) ;
break ;
case 2 :
retval = fs_name ( arg1 , ( char __user * ) arg2 ) ;
break ;
case 3 :
retval = fs_maxindex ( ) ;
break ;
}
return retval ;
}
2009-04-09 15:17:52 +04:00
int __init get_filesystem_list ( char * buf )
2005-04-17 02:20:36 +04:00
{
int len = 0 ;
struct file_system_type * tmp ;
read_lock ( & file_systems_lock ) ;
tmp = file_systems ;
while ( tmp & & len < PAGE_SIZE - 80 ) {
len + = sprintf ( buf + len , " %s \t %s \n " ,
( tmp - > fs_flags & FS_REQUIRES_DEV ) ? " " : " nodev " ,
tmp - > name ) ;
tmp = tmp - > next ;
}
read_unlock ( & file_systems_lock ) ;
return len ;
}
2008-10-04 14:08:37 +04:00
# ifdef CONFIG_PROC_FS
static int filesystems_proc_show ( struct seq_file * m , void * v )
{
struct file_system_type * tmp ;
read_lock ( & file_systems_lock ) ;
tmp = file_systems ;
while ( tmp ) {
seq_printf ( m , " %s \t %s \n " ,
( tmp - > fs_flags & FS_REQUIRES_DEV ) ? " " : " nodev " ,
tmp - > name ) ;
tmp = tmp - > next ;
}
read_unlock ( & file_systems_lock ) ;
return 0 ;
}
static int filesystems_proc_open ( struct inode * inode , struct file * file )
{
return single_open ( file , filesystems_proc_show , NULL ) ;
}
static const struct file_operations filesystems_proc_fops = {
. open = filesystems_proc_open ,
. read = seq_read ,
. llseek = seq_lseek ,
. release = single_release ,
} ;
static int __init proc_filesystems_init ( void )
{
proc_create ( " filesystems " , 0 , NULL , & filesystems_proc_fops ) ;
return 0 ;
}
module_init ( proc_filesystems_init ) ;
# endif
2008-12-25 08:32:15 +03:00
static struct file_system_type * __get_fs_type ( const char * name , int len )
2005-04-17 02:20:36 +04:00
{
struct file_system_type * fs ;
read_lock ( & file_systems_lock ) ;
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:25:43 +04:00
fs = * ( find_filesystem ( name , len ) ) ;
2005-04-17 02:20:36 +04:00
if ( fs & & ! try_module_get ( fs - > owner ) )
fs = NULL ;
read_unlock ( & file_systems_lock ) ;
2008-12-25 08:32:15 +03:00
return fs ;
}
struct file_system_type * get_fs_type ( const char * name )
{
struct file_system_type * fs ;
const char * dot = strchr ( name , ' . ' ) ;
int len = dot ? dot - name : strlen ( name ) ;
fs = __get_fs_type ( name , len ) ;
if ( ! fs & & ( request_module ( " %.*s " , len , name ) = = 0 ) )
fs = __get_fs_type ( name , len ) ;
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:25:43 +04:00
if ( dot & & fs & & ! ( fs - > fs_flags & FS_HAS_SUBTYPE ) ) {
put_filesystem ( fs ) ;
fs = NULL ;
}
2005-04-17 02:20:36 +04:00
return fs ;
}
EXPORT_SYMBOL ( get_fs_type ) ;