linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Gertjan Oude Lohuis <gertjan@oudelohuis.nl>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: Adding mount option to kernel for NFS filesystem
Date: Wed, 29 Apr 2009 13:02:26 -0400	[thread overview]
Message-ID: <1241024546.12464.17.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <49F86F5A.7030903@oudelohuis.nl>

On Wed, 2009-04-29 at 17:16 +0200, Gertjan Oude Lohuis wrote:
> Hi guys,
> 
> For fun and learning purposes I'm trying to add an mountflag for 
> NFS-mounts to the kernel and mount. The flag's semantics are identical 
> to ac/noac: 'flag' is default but has no special meaning, 'noflag' 
> triggers a certain action.
> 
> I have a small question about adding the flag to 
> include/linux/nfs_mount.h. Since NFS_MOUNT_FLAGMASK is defined as 
> 0xFFFF, and all bits up until 0xFFFF are occupied by existing 
> NFS_MOUNT-flags, how could I add my own flag?
> Would it be ok to define NFS_MOUNT_FLAGMASK as 0xFFFFF and my own flag 
> as 0x10000? Or will this have other side effects? It seems to be working 
> though ;-).
> How would this be done if a real flag should be added by kernel maintainers?

The policy is that we don't add any more flags or features to the legacy
binary mount interface. NFS_MOUNT_FLAGMASK is there to enforce that
rule, so changing it is not acceptable.

All new mount features should be added using the text-based mount
interface (see nfs_parse_mount_options()), which is supported by recent
versions of the mount.nfs program in the nfs-utils package.

Cheers
  Trond


  reply	other threads:[~2009-04-29 17:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-29 15:16 Adding mount option to kernel for NFS filesystem Gertjan Oude Lohuis
2009-04-29 17:02 ` Trond Myklebust [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-04-29 17:03 Gertjan Oude Lohuis
     [not found] ` <49F8884A.8050402-yZ1RIXqxfwWWrUy98/Atqw@public.gmane.org>
2009-04-30 18:58   ` Jeff Layton

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=1241024546.12464.17.camel@heimdal.trondhjem.org \
    --to=trond.myklebust@fys.uio.no \
    --cc=gertjan@oudelohuis.nl \
    --cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).