From: Andreas Gruenbacher <agruen@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: "Aurélien Francillon" <aurel@naurel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Olaf Kirch" <okir@suse.de>
Subject: Re: 2.6.11-rc5-mm1
Date: Wed, 02 Mar 2005 16:45:53 +0100 [thread overview]
Message-ID: <1109778352.22077.155.camel@winden.suse.de> (raw)
In-Reply-To: <20050302005344.1c3420db.akpm@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 1084 bytes --]
Hello,
On Wed, 2005-03-02 at 09:53, Andrew Morton wrote:
> Aurélien Francillon <aurel@naurel.org> wrote:
> > [...]
> > cvs diff Makefile
> > cvs diff: cannot create read lock in repository
> > `/mnt/iseran/roca/cvsroot/ldpc': No such file or directory
> > cvs [diff aborted]: read lock failed - giving up
> >
> > but the file is created and i can "cat " it without problem ...
This fixes it:
Index: linux-2.6.11/fs/nfs/nfs3proc.c
===================================================================
--- linux-2.6.11.orig/fs/nfs/nfs3proc.c
+++ linux-2.6.11/fs/nfs/nfs3proc.c
@@ -423,6 +423,9 @@ exit:
if (!inode)
goto out;
status = nfs3_set_default_acl(dir, inode, mode);
+ if (status)
+ goto out;
+ return inode;
}
out:
return ERR_PTR(status);
I'll reply to this message with an updated patch:
Re: [nfsacl v2 15/16] ACL umask handling workaround in nfs client
Regards,
--
Andreas Gruenbacher <agruen@suse.de>
SUSE Labs, SUSE LINUX GMBH
[-- Attachment #2: nfsacl-acl-umask-handling-workaround-in-nfs-client-3.patch --]
[-- Type: message/rfc822, Size: 4882 bytes --]
From: Andreas Gruenbacher <agruen@suse.de>
Subject: ACL umask handling workaround in nfs client
Date: Wed, 02 Mar 2005 16:41:47 +0100
Message-ID: <1109778107.22077.150.camel@winden.suse.de>
NFSv3 has no concept of a umask on the server side: The client applies
the umask locally, and sends the effective permissions to the server.
This behavior is wrong when files are created in a directory that has a
default ACL. In this case, the umask is supposed to be ignored, and
only the default ACL determines the file's effective permissions.
Usually its the server's task to conditionally apply the umask. But
since the server knows nothing about the umask, we have to do it on the
client side. This patch tries to fetch the parent directory's default
ACL before creating a new file, computes the appropriate create mode to
send to the server, and finally sets the new file's access and default
acl appropriately.
Many thanks to Buck Huppmann <buchk@pobox.com> for sending the initial
version of this patch, as well as for arguing why we need this change.
Signed-off-by: Andreas Gruenbacher <agruen@suse.de>
Acked-by: Olaf Kirch <okir@suse.de>
Index: linux-2.6.11/fs/nfs/nfs3proc.c
===================================================================
--- linux-2.6.11.orig/fs/nfs/nfs3proc.c
+++ linux-2.6.11/fs/nfs/nfs3proc.c
@@ -292,6 +292,38 @@ static int nfs3_proc_commit(struct nfs_w
return status;
}
+static int nfs3_set_default_acl(struct inode *dir, struct inode *inode,
+ mode_t mode)
+{
+#ifdef CONFIG_NFS_ACL
+ struct posix_acl *dfacl, *acl;
+ int error = 0;
+
+ dfacl = NFS_PROTO(dir)->getacl(dir, ACL_TYPE_DEFAULT);
+ if (IS_ERR(dfacl)) {
+ error = PTR_ERR(dfacl);
+ return (error == -EOPNOTSUPP) ? 0 : error;
+ }
+ if (!dfacl)
+ return 0;
+ acl = posix_acl_clone(dfacl, GFP_KERNEL);
+ error = -ENOMEM;
+ if (!acl)
+ goto out;
+ error = posix_acl_create_masq(acl, &mode);
+ if (error < 0)
+ goto out;
+ error = NFS_PROTO(inode)->setacls(inode, acl, S_ISDIR(inode->i_mode) ?
+ dfacl : NULL);
+out:
+ posix_acl_release(acl);
+ posix_acl_release(dfacl);
+ return error;
+#else
+ return 0;
+#endif
+}
+
/*
* Create a regular file.
* For now, we don't implement O_EXCL.
@@ -314,8 +346,12 @@ nfs3_proc_create(struct inode *dir, stru
.fh = &fhandle,
.fattr = &fattr
};
+ mode_t mode;
int status;
+ mode = sattr->ia_mode;
+ sattr->ia_mode &= ~current->fs->umask;
+
dprintk("NFS call create %s\n", dentry->d_name.name);
arg.createmode = NFS3_CREATE_UNCHECKED;
if (flags & O_EXCL) {
@@ -350,7 +386,6 @@ again:
exit:
dprintk("NFS reply create: %d\n", status);
-
if (status != 0)
goto out;
if (fhandle.size == 0 || !(fattr.valid & NFS_ATTR_FATTR)) {
@@ -384,9 +419,13 @@ exit:
if (status == 0) {
struct inode *inode;
inode = nfs_fhget(dir->i_sb, &fhandle, &fattr);
- if (inode)
- return inode;
status = -ENOMEM;
+ if (!inode)
+ goto out;
+ status = nfs3_set_default_acl(dir, inode, mode);
+ if (status)
+ goto out;
+ return inode;
}
out:
return ERR_PTR(status);
@@ -556,8 +595,12 @@ nfs3_proc_mkdir(struct inode *dir, struc
.fh = &fh,
.fattr = &fattr
};
+ mode_t mode;
int status;
+ mode = sattr->ia_mode;
+ sattr->ia_mode &= ~current->fs->umask;
+
dprintk("NFS call mkdir %s\n", dentry->d_name.name);
dir_attr.valid = 0;
fattr.valid = 0;
@@ -566,6 +609,8 @@ nfs3_proc_mkdir(struct inode *dir, struc
if (!status)
status = nfs_instantiate(dentry, &fh, &fattr);
dprintk("NFS reply mkdir: %d\n", status);
+ if (!status)
+ status = nfs3_set_default_acl(dir, dentry->d_inode, mode);
return status;
}
@@ -659,6 +704,7 @@ nfs3_proc_mknod(struct inode *dir, struc
.fh = &fh,
.fattr = &fattr
};
+ mode_t mode;
int status;
switch (sattr->ia_mode & S_IFMT) {
@@ -669,6 +715,9 @@ nfs3_proc_mknod(struct inode *dir, struc
default: return -EINVAL;
}
+ mode = sattr->ia_mode;
+ sattr->ia_mode &= ~current->fs->umask;
+
dprintk("NFS call mknod %s %u:%u\n", dentry->d_name.name,
MAJOR(rdev), MINOR(rdev));
dir_attr.valid = 0;
@@ -678,6 +727,8 @@ nfs3_proc_mknod(struct inode *dir, struc
if (!status)
status = nfs_instantiate(dentry, &fh, &fattr);
dprintk("NFS reply mknod: %d\n", status);
+ if (!status)
+ status = nfs3_set_default_acl(dir, dentry->d_inode, mode);
return status;
}
Index: linux-2.6.11/fs/nfs/inode.c
===================================================================
--- linux-2.6.11.orig/fs/nfs/inode.c
+++ linux-2.6.11/fs/nfs/inode.c
@@ -485,6 +485,8 @@ nfs_fill_super(struct super_block *sb, s
server->client_acl = clnt;
/* Initially assume the nfsacl program is supported */
server->flags |= NFSACL;
+ /* The nfs client applies the umask itself when needed. */
+ sb->s_flags |= MS_POSIXACL;
}
#endif
if (server->flags & NFS_MOUNT_VER3) {
next prev parent reply other threads:[~2005-03-02 15:47 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-01 9:27 2.6.11-rc5-mm1 Andrew Morton
2005-03-01 13:36 ` 2.6.11-rc5-mm1 Valdis.Kletnieks
2005-03-01 13:55 ` 2.6.11-rc5-mm1 Russell King
2005-03-01 15:18 ` 2.6.11-rc5-mm1 Valdis.Kletnieks
2005-03-01 15:27 ` 2.6.11-rc5-mm1 Russell King
2005-03-01 20:42 ` 2.6.11-rc5-mm1 Andrew Morton
2005-03-01 20:45 ` 2.6.11-rc5-mm1 Greg KH
2005-03-01 13:53 ` 2.6.11-rc5-mm1 Mathieu Segaud
2005-03-01 14:00 ` 2.6.11-rc5-mm1 Mathieu Segaud
2005-03-01 14:06 ` 2.6.11-rc5-mm1 Mathieu Segaud
2005-03-01 15:06 ` 2.6.11-rc5-mm1 Edward Shishkin
2005-03-01 15:53 ` 2.6.11-rc5-mm1 (compile stats) John Cherry
2005-03-01 17:40 ` 2.6.11-rc5-mm1 Aurélien Francillon
2005-03-02 8:53 ` 2.6.11-rc5-mm1 Andrew Morton
2005-03-02 15:45 ` Andreas Gruenbacher [this message]
2005-03-03 11:01 ` 2.6.11-rc5-mm1 Aurélien Francillon
2005-03-01 20:16 ` 2.6.11-rc5-mm1 Adrian Bunk
2005-03-01 21:58 ` 2.6.11-rc5-mm1 Andrew Morton
2005-03-01 21:49 ` 2.6.11-rc5-mm1 Chris Wright
2005-03-01 22:08 ` 2.6.11-rc5-mm1 Andrew Morton
2005-03-03 8:04 ` 2.6.11-rc5-mm1 Jeff Dike
2005-03-03 16:21 ` 2.6.11-rc5-mm1 Chris Wright
2005-03-03 19:25 ` 2.6.11-rc5-mm1 Jeff Dike
2005-03-03 19:14 ` 2.6.11-rc5-mm1 Chris Wright
2005-03-04 11:01 ` 2.6.11-rc5-mm1 zwx
2005-03-01 23:43 ` [2.6.11-rc5-mm1 patch] reiser4 Kconfig help cleanup Adrian Bunk
2005-03-02 9:01 ` Jes Sorensen
2005-03-02 9:14 ` Andrew Morton
2005-03-02 14:29 ` Nikita Danilov
2005-03-02 14:40 ` [2.6.11-rc5-mm1 patch] reiser4 cleanup (PG_arch_1) Vladimir Saveliev
2005-03-03 13:17 ` [2.6.11-rc5-mm1 patch] fs/reiser4/: possible cleanups Adrian Bunk
2005-03-03 13:22 ` [2.6.11-rc5-mm1 patch] drivers/acpi/pcc_acpi.c: section fixes Adrian Bunk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1109778352.22077.155.camel@winden.suse.de \
--to=agruen@suse.de \
--cc=akpm@osdl.org \
--cc=aurel@naurel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=okir@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox