Ned Bass da29fe63f0 Don't leak mount flags into kernel ... When calling mount(), care must be taken to avoid passing in flags that are used only by the user space utilities. Otherwise we may stomp on flags that are reserved for other purposes in the kernel. In particular, openSUSE 12.3 kernels have added a new MS_RICHACL super-block flag whose value conflicts with our MS_COMMENT flag. This causes incorrect behavior such as the umask being ignored. The MS_COMMENT flag essentially serves as a placeholder in the option_map data structure of zfs_mount.c, but its value is never used. Therefore we can avoid the conflict by defining it to 0. The MS_USERS, MS_OWNER, and MS_GROUP flags also conflict with reserved flags in the kernel. While this is not known to have caused any problems, it is nevertheless incorrect. For the purposes of the mount.zfs helper, the "users", "owner", and "group" options just serve as hints to set additional implied options. Therefore we now define their associated mount flags in terms of the options that they imply rather than giving them unique values. Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Closes #1457		2013-06-18 15:30:08 -07:00
..
.gitignore	Added .gitignore for mount.zfs and zvol_id	2011-04-07 10:28:38 -07:00
Makefile.am	Add libnvpair to mount_zfs dependencies	2012-09-02 15:36:09 -07:00
mount_zfs.c	Don't leak mount flags into kernel	2013-06-18 15:30:08 -07:00