From: Jeff Layton <jlayton@redhat.com>
To: Gertjan Oude Lohuis <gertjan-yZ1RIXqxfwWWrUy98/Atqw@public.gmane.org>
Cc: linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: Adding mount option to kernel for NFS filesystem
Date: Thu, 30 Apr 2009 14:58:16 -0400 [thread overview]
Message-ID: <20090430145816.7761131b@barsoom.rdu.redhat.com> (raw)
In-Reply-To: <49F8884A.8050402-yZ1RIXqxfwWWrUy98/Atqw@public.gmane.org>
On Wed, 29 Apr 2009 19:03:06 +0200
Gertjan Oude Lohuis <gertjan-yZ1RIXqxfwWWrUy98/Atqw@public.gmane.org> 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?
>
> I guess another option would be to create a new entry in the
> nfs_mount_data struct and treat it as an option (rsize-, wsize-,
> timeo-alike), but I'd like to do keep it the same as other flags.
>
> Please advice! ;-)
> Thanks in advance for your time.
>
> Sincerely,
> Gertjan
>
It's probably better to post questions like this to
linux-nfs-u79uwXL29TaiAVqoAR/hOA@public.gmane.org cc'ing that on the response...
Newer kernels and mount.nfs progs use text-based mount options by
default. My suggestion would be to avoid worrying about the legacy
mount option code and to just make the new option work with the text
based ones only.
Cheers,
--
Jeff Layton <jlayton@redhat.com>
parent reply other threads:[~2009-04-30 18:58 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <49F8884A.8050402-yZ1RIXqxfwWWrUy98/Atqw@public.gmane.org>]
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=20090430145816.7761131b@barsoom.rdu.redhat.com \
--to=jlayton@redhat.com \
--cc=gertjan-yZ1RIXqxfwWWrUy98/Atqw@public.gmane.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@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