linux-ext4 - Mount option "grpid" scheduled for removal?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Thu, 7 Jul 2011 11:14:08 +0200
From:	Frank van Maarseveen <frankvm@...nkvm.com>
To:	linux-ext4@...r.kernel.org
Subject: Mount option "grpid" scheduled for removal?

2.6.39.2:

kernel: EXT4-fs (dm-0): Mount option "grpid" will be removed by 2.6.38
kernel: Contact linux-ext4@...r.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
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html