From: Benjamin Coddington <bcodding@redhat.com>
To: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Historical reason for NFS_MOUNT_FLAGMASK?
Date: Wed, 12 Mar 2025 11:23:09 -0400 [thread overview]
Message-ID: <37CB7B45-A199-4815-8D4A-95D06CDA2D0C@redhat.com> (raw)
I'm looking for some bits in the nfs_mount_data.flags, and wondering why we
have only 16 bits masked off due to:
#define NFS_MOUNT_FLAGMASK 0xFFFF
Does anyone recall why we've limited the ABI to 16 bits here?
Ben
next reply other threads:[~2025-03-12 15:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 15:23 Benjamin Coddington [this message]
2025-03-12 20:15 ` Historical reason for NFS_MOUNT_FLAGMASK? Benjamin Coddington
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=37CB7B45-A199-4815-8D4A-95D06CDA2D0C@redhat.com \
--to=bcodding@redhat.com \
--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