lkml.org 
[lkml]   [2005]   [Aug]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [RFC][PATCH] VFS: update documentation (take #2)
From
Date
on den 24.08.2005 Klokka 21:36 (+0300) skreiv Pekka Enberg:
>
> struct file_system_type {
> const char *name;
> int fs_flags;
> - struct super_block *(*read_super) (struct super_block *, void *, int);
> - struct file_system_type * next;
> + struct super_block *(*get_sb) (struct file_system_type *, int,
> + const char *, void *);
> + void (*kill_sb) (struct super_block *);
> + struct module *owner;
> + struct file_system_type * next;
> + struct list_head fs_supers;
> };
>
> name: the name of the filesystem type, such as "ext2", "iso9660",
> @@ -141,51 +141,96 @@ struct file_system_type {
>
> fs_flags: various flags (i.e. FS_REQUIRES_DEV, FS_NO_DCACHE, etc.)
>
> - read_super: the method to call when a new instance of this
> + get_sb: the method to call when a new instance of this
> filesystem should be mounted
>
> - next: for internal VFS use: you should initialise this to NULL
> + kill_sb: the method to call when an instance of this filesystem
> + should be unmounted
> +
> + owner: for internal VFS use: you should initialize this to NULL

owner should be set to THIS_MODULE in most cases...

Cheers,
Trond

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

\
 
 \ /
  Last update: 2005-08-24 20:49    [W:0.039 / U:0.144 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site