fuse2fs: respect requested mode in mkdir

At the moment, op_mkdir() ORs the requested mode with fs->umask, which
results in the group/other write permission bits always being cleared
regardless of what the creating process requested.  Instead, leave the
requested mode alone so that the resulting directory has the permssions
the creator expects.

Signed-off-by: Steven Luo <steven@steven676.net>

diff --git a/misc/fuse2fs.c b/misc/fuse2fs.c
index 0dc77eadc53c3b22aea3a0a5ed1923d67ea96633..0eb216217b15d564d8d3b76fa63c6928d8ebe68b 100644 (file)
--- a/misc/fuse2fs.c
+++ b/misc/fuse2fs.c
@@ -1129,7 +1129,7 @@ static int op_mkdir(const char *path, mode_t mode)
        ext2fs_set_i_uid_high(inode, ctxt->uid >> 16);
        inode.i_gid = ctxt->gid;
        ext2fs_set_i_gid_high(inode, ctxt->gid >> 16);
-       inode.i_mode = LINUX_S_IFDIR | (mode & ~(S_ISUID | fs->umask)) |
+       inode.i_mode = LINUX_S_IFDIR | (mode & ~S_ISUID) |
                       parent_sgid;
        inode.i_generation = ff->next_generation++;