linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: hch@lst.de
Cc: linux-fsdevel@vger.kernel.org, nfs@lists.sourceforge.net
Subject: Re: [PATCH 19/19] exportfs: update documentation
Date: Fri, 14 Sep 2007 14:24:57 -0700	[thread overview]
Message-ID: <20070914142457.d96c9924.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20070914114928.GT28282@lst.de>

On Fri, 14 Sep 2007 13:49:28 +0200 hch@lst.de wrote:

typos only below:


> Update deocumentation to the current state of affairs.  Remove duplicated
> method descruptions in exportfs.h and point to Documentation/filesystems/
> Exporting instead.  Add a little file header comment in expfs.c describing
> what's going on and mentioning Neils and my copyright [1].
> 
> [1] Neil, in case you want a different/additional attribution just change
>     the patch in your queue to reflect the preferred version.
> 
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> 
> Index: linux-2.6/Documentation/filesystems/Exporting
> ===================================================================
> --- linux-2.6.orig/Documentation/filesystems/Exporting	2007-03-16 15:10:54.000000000 +0100
> +++ linux-2.6/Documentation/filesystems/Exporting	2007-03-16 17:11:50.000000000 +0100
> + encode_fh  (optinonal)

               (optional)

> +    Takes a dentry and creates a filehandle fragment which can later be used
> +    to find/create a dentry for the same object.  The default implementation
> +    creates a filehandle fragment that encodes a 32bit inode and generation
> +    number for the inode encoded, and if nessecary the same information for

                                            necessary

> +    the parent.
> +
> +  fh_to_dentry (mandatory)
> +    Given a filehandle fragment, this should find the implied object and
> +    create a dentry for it (possibly with d_alloc_anon).
> +
> +  fh_to_parent (optional but strongly recommended)
> +    Given a filehandle fragment, this should find the parent of the
> +    implied object and create a dentry for it (possibly with d_alloc_anon).
> +    May simplify fail if the filehandle fragment is too small.\

           simply  (?)

> +
> +  get_parent (optional but strongly recommended)
> +    When given a dentry for a directory, this should return  a dentry for
> +    the parent.  Quite possibly the parent dentry will have been allocated
> +    by d_alloc_anon.  The default get_parent function just returns an error
> +    so any filehandle lookup that requires finding a parent will fail.
> +    ->lookup("..") is *not* used as a default as it can leave ".." entries
> +    in the dcache which are too messy to work with.

> Index: linux-2.6/fs/exportfs/expfs.c
> ===================================================================
> --- linux-2.6.orig/fs/exportfs/expfs.c	2007-03-16 17:06:10.000000000 +0100
> +++ linux-2.6/fs/exportfs/expfs.c	2007-03-16 23:45:14.000000000 +0100
> @@ -1,4 +1,13 @@
> -
> +/*
> + * Copyright (C) Neil Brown 2002
> + * Copyright (C) Christoph Hellwig 2007
> + *
> + * This file contains the code mapping from inodes to NFS file handles,
> + * and for mapping back from file handles to dentries.
> + *
> + * For details on why we doo all the strange and hairy things in here

                            do

> + * take a look at Documentation/filesystems/Exporting.
> + */
>  #include <linux/exportfs.h>
>  #include <linux/fs.h>
>  #include <linux/file.h>


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

      reply	other threads:[~2007-09-14 21:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-14 11:49 [PATCH 19/19] exportfs: update documentation hch
2007-09-14 21:24 ` Randy Dunlap [this message]

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=20070914142457.d96c9924.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=nfs@lists.sourceforge.net \
    /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).