From 702b2912970e7cc19416aff7d3696d15977efc2f Mon Sep 17 00:00:00 2001 From: Niels de Vos Date: Fri, 9 Nov 2012 14:43:38 +0100 Subject: fuse: handle mountflags properly The internal mount API had no access to the generic mountflags used by mount(2). Thus the "ro" mount option that needs to be passed down to mount(2) as as a mountflag was incorrectly mangled into the fuse-specific mount parameter string (cf. http://review.gluster.com/655). This commit fixes the internal API and the "ro" issue. It also adds a check for the "rw" and "ro" mount options in tests/basic/mount.t. Thanks to Csaba Henk (csaba@) for suggestions and proposing an updated patch. Change-Id: I7f7bf49ae44d148f5c16f10736a0e412fb8f5e67 BUG: 853895 Signed-off-by: Niels de Vos Reviewed-on: http://review.gluster.org/4163 Reviewed-by: Csaba Henk Tested-by: Gluster Build System --- contrib/fuse-include/fuse-mount.h | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'contrib/fuse-include/fuse-mount.h') diff --git a/contrib/fuse-include/fuse-mount.h b/contrib/fuse-include/fuse-mount.h index 7a3756d92b8..9358ac810e1 100644 --- a/contrib/fuse-include/fuse-mount.h +++ b/contrib/fuse-include/fuse-mount.h @@ -8,5 +8,6 @@ */ void gf_fuse_unmount (const char *mountpoint, int fd); -int gf_fuse_mount (const char *mountpoint, char *fsname, char *mnt_param, +int gf_fuse_mount (const char *mountpoint, char *fsname, + unsigned long mountflags, char *mnt_param, pid_t *mtab_pid, int status_fd); -- cgit