Re: [PATCH 2/5] ceph: Propagate dentry down to inode_change_ok()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 2016-09-19 at 17:30 +0200, Jan Kara wrote:
> To avoid clearing of capabilities or security related extended
> attributes too early, inode_change_ok() will need to take dentry instead
> of inode. ceph_setattr() has the dentry easily available but
> __ceph_setattr() is also called from ceph_set_acl() where dentry is not
> easily available. Luckily that call path does not need inode_change_ok()
> to be called anyway. So reorganize functions a bit so that
> inode_change_ok() is called only from paths where dentry is available.
> 
> > Signed-off-by: Jan Kara <jack@xxxxxxx>
> ---
>  fs/ceph/acl.c   |  5 +++++
>  fs/ceph/inode.c | 19 +++++++++++--------
>  2 files changed, 16 insertions(+), 8 deletions(-)
> 
> diff --git a/fs/ceph/acl.c b/fs/ceph/acl.c
> index 013151d50069..a2cedfde75eb 100644
> --- a/fs/ceph/acl.c
> +++ b/fs/ceph/acl.c
> @@ -127,6 +127,11 @@ int ceph_set_acl(struct inode *inode, struct posix_acl *acl, int type)
> >  			goto out_free;
> >  	}
>  
> > +	if (ceph_snap(inode) != CEPH_NOSNAP) {
> > +		ret = -EROFS;
> > +		goto out_free;
> > +	}
> +

So to make sure I understand: What's the expected behavior when someone
changes the ACL in such a way that the mode gets changed? Should
security_inode_killpriv be getting called in that case? If so, where
does that happen, as I don't see notify_change being called in this
codepath?

>  	if (new_mode != old_mode) {
> >  		newattrs.ia_mode = new_mode;
> >  		newattrs.ia_valid = ATTR_MODE;
> diff --git a/fs/ceph/inode.c b/fs/ceph/inode.c
> index dd3a6dbf71eb..2aa3c0bcf3a5 100644
> --- a/fs/ceph/inode.c
> +++ b/fs/ceph/inode.c
> @@ -1905,13 +1905,6 @@ int __ceph_setattr(struct inode *inode, struct iattr *attr)
> >  	int inode_dirty_flags = 0;
> >  	bool lock_snap_rwsem = false;
>  
> > -	if (ceph_snap(inode) != CEPH_NOSNAP)
> > -		return -EROFS;
> -
> > -	err = inode_change_ok(inode, attr);
> > -	if (err != 0)
> > -		return err;
> -
> >  	prealloc_cf = ceph_alloc_cap_flush();
> >  	if (!prealloc_cf)
> >  		return -ENOMEM;
> @@ -2124,7 +2117,17 @@ out_put:
>   */
>  int ceph_setattr(struct dentry *dentry, struct iattr *attr)
>  {
> > -	return __ceph_setattr(d_inode(dentry), attr);
> > +	struct inode *inode = d_inode(dentry);
> > +	int err;
> +
> > +	if (ceph_snap(inode) != CEPH_NOSNAP)
> > +		return -EROFS;
> +
> > +	err = inode_change_ok(inode, attr);
> > +	if (err != 0)
> > +		return err;
> +
> > +	return __ceph_setattr(inode, attr);
>  }
>  
>  /*

Looks reasonable though:

Acked-by: Jeff Layton <jlayton@xxxxxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux