linux-kernel - Re: [patch 05/10] Add "permit user submounts" flag to vfsmount

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <E1HdlAt-00013a-00@dorka.pomaz.szeredi.hu>
Date:	Tue, 17 Apr 2007 12:44:39 +0200
From:	Miklos Szeredi <miklos@...redi.hu>
To:	serue@...ibm.com
CC:	akpm@...ux-foundation.org, viro@....linux.org.uk,
	linuxram@...ibm.com, ebiederm@...ssion.com,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
	containers@...ts.osdl.org
Subject: Re: [patch 05/10] Add "permit user submounts" flag to vfsmount

> > From: Miklos Szeredi <mszeredi@...e.cz>
> > 
> > If MNT_USERMNT flag is not set in the target vfsmount, then
> 
> MNT_USER and MNT_USERMNT?  I claim no way will people keep those
> straight.  How about MNT_ALLOWUSER and MNT_USER?

Umm, is "allowuser" more clear than "usermnt"?  What is allowed to the
user?  "allowusermnt" may be more descriptive, but it's a bit too
long.

I don't think it matters all that much, the user will have to look up
the semantics in the manpage anyway.  Is "nosuid" descriptive?  Not
very much, but we got used to it.

Miklos
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/