Linux NFS development
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Shehjar Tikoo <shehjart-YbfuJp6tym7X/JP9YwkgDA@public.gmane.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Doc for adding new NFS export option
Date: Mon, 7 Jul 2008 16:29:21 +1000	[thread overview]
Message-ID: <18545.47041.516146.605353@notabene.brown> (raw)
In-Reply-To: message from Shehjar Tikoo on Monday July 7

On Monday July 7, shehjart-YbfuJp6tym7X/JP9YwkgDA@public.gmane.org wrote:
> Hi All
> 
> Is there a document that enumerates which files and functions I need 
> to add stuff to, for adding a new server-side export option?

No.  I think the theory is that unless you have read and understood
the code, you should really be thinking about adding new options.
And if you have, then you don't need any documentations.
:-)

> 
> I've tried adding it to some of the functions in the exportfs related 
> code in nfs-utils and also in the kernel's export related headers but 
> I dont think that is all there is to it.

That sounds good, but without details, it is hard to be sure.
Don't be afraid to send a patch which shows what you are trying to do.

> 
> I ask this because without my new option, I am able to mount the 
> export correctly but with it, the mount command fails with the 
> following message:
> 
> mount.nfs: 192.168.10.5:/data/nfstest failed, reason given by server: 
> Permission denied

So what exactly is this new export option that you want to add?

NeilBrown

  reply	other threads:[~2008-07-07  6:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-07  3:39 Doc for adding new NFS export option Shehjar Tikoo
2008-07-07  6:29 ` Neil Brown [this message]
     [not found]   ` <18545.47041.516146.605353-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-07-09  2:45     ` Shehjar Tikoo
2008-07-09  3:58       ` Neil Brown
     [not found]         ` <18548.14177.493986.264761-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-07-09 15:02           ` J. Bruce Fields
2008-07-09 22:30           ` Shehjar Tikoo
     [not found]             ` <48753C1A.3030402-YbfuJp6tym7X/JP9YwkgDA@public.gmane.org>
2008-07-09 23:40               ` Chuck Lever
     [not found]                 ` <76bd70e30807091640q179617b8s749742bd2f10097d-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-07-10 23:40                   ` Shehjar Tikoo
     [not found]                     ` <48769E02.3020900-YbfuJp6tym7X/JP9YwkgDA@public.gmane.org>
2008-07-11  4:31                       ` Chuck Lever
     [not found]                         ` <76bd70e30807102131w190145d7nece35402050be860-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-07-11 12:32                           ` Shehjar Tikoo

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=18545.47041.516146.605353@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-nfs@vger.kernel.org \
    --cc=shehjart-YbfuJp6tym7X/JP9YwkgDA@public.gmane.org \
    /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