linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC][PATCH] VFS: update documentation (take #2)
Date: Wed, 24 Aug 2005 11:46:30 -0700	[thread overview]
Message-ID: <1124909191.8286.2.camel@lade.trondhjem.org> (raw)
In-Reply-To: <1124908580.18800.2.camel@localhost>

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

  reply	other threads:[~2005-08-24 18:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-24 18:36 [RFC][PATCH] VFS: update documentation (take #2) Pekka Enberg
2005-08-24 18:46 ` Trond Myklebust [this message]
2005-08-24 19:56 ` Anton Altaparmakov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1124909191.8286.2.camel@lade.trondhjem.org \
    --to=trond.myklebust@fys.uio.no \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).