From: Frank van Maarseveen <frankvm@frankvm.com>
To: linux-ext4@vger.kernel.org
Subject: Mount option "grpid" scheduled for removal?
Date: Thu, 7 Jul 2011 11:14:08 +0200 [thread overview]
Message-ID: <20110707091408.GA1102@janus> (raw)
2.6.39.2:
kernel: EXT4-fs (dm-0): Mount option "grpid" will be removed by 2.6.38
kernel: Contact linux-ext4@vger.kernel.org if you think we should keep it.
Is it still scheduled for removal?
Are there technical reasons why it should be removed from an otherwise
excellent backwards compatible filesystem?
Is it also removed from the ext[23] implementation in ext4?
The grpid option is used in a large ext3/ext4 NFS server setup and I'm
aware of the sysv setgid alternative but:
- Replacing grpid by setgid on directories requires an off-line
conversion.
- grpid and setgid on directories are not the same so it can
break things.
Processes calling chmod() will break group inheritance unless they are
carefully written to only update permission bits. Those programs will
still break when run on an NFS client when the user is not a member of
the group. Repairing the setgid bit requires group membership too.
I'm not saying it's impossible to replace grpid by setgid on directories
but it requires some work and it still can break unexpectedly.
--
Frank
reply other threads:[~2011-07-07 9:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20110707091408.GA1102@janus \
--to=frankvm@frankvm.com \
--cc=linux-ext4@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).