xfs
[Top] [All Lists]

Re: [PATCH v7 0/7] userns: Convert xfs to use kuid_t/kgid_t where approp

To: Dwight Engen <dwight.engen@xxxxxxxxxx>
Subject: Re: [PATCH v7 0/7] userns: Convert xfs to use kuid_t/kgid_t where appropriate
From: Gao feng <gaofeng@xxxxxxxxxxxxxx>
Date: Wed, 31 Jul 2013 14:30:38 +0800
Cc: xfs@xxxxxxxxxxx, Dave Chinner <david@xxxxxxxxxxxxx>, Brian Foster <bfoster@xxxxxxxxxx>, Serge Hallyn <serge.hallyn@xxxxxxxxxx>, "Eric W. Biederman" <ebiederm@xxxxxxxxx>
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <20130729230633.725a282e@xxxxxxxxxx>
References: <20130729230633.725a282e@xxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7
Hi Dwight,

On 07/30/2013 11:06 AM, Dwight Engen wrote:
> Hi All,
> 
> This updated patchset is on top of ad81f054 of xfs git (3.11-rc1). The
> patches do not convert the id's returned from bulkstat, since bulkstat
> cannot be called from inside a userns right now anyway since the caller
> must be CAP_SYS_ADMIN in init_user_ns.


As I method in another mail thread, I found the changing projid of file in 
container
hasn't been disallowed. it means the user in container can change file's projid.
so the project quota won't take effect.

the project quota info before I change file's projid in container:

Project quota on /media/lw (/dev/sdc1)
                        Blocks
Project ID   Used   Soft   Hard Warn/Grace
---------- ---------------------------------
testproj      64K   100M   110M  00 [------]


and after I use a simple program which execs the below code.

fa.fsx_projid = 21; // different projid from testproj
fa.fsx_xflags &= ~XFS_XFLAG_IMMUTABLE;
ret = xfsctl("/mount_point_of_xfs", fd, XFS_IOC_FSSETXATTR, &fa);

the project quota becomes to:

Project quota on /media/lw (/dev/sdc1)
                        Blocks
Project ID   Used   Soft   Hard Warn/Grace
---------- ---------------------------------
testproj      60K   100M   110M  00 [------]


So I think we still need a patch to reduce the changing-project-id
rights of un-init user namespace.

Thanks


> 
> Changes since v6 patchset (addressing Dave's comments)
> - 0006 just do a capable(CAP_SYS_ADMIN) check for XFS_IOC_FREE_EOFBLOCKS
> 
> Changes since v5 patchset (addressing Brian's comments,
> only 0005 and 0006 are changed):
>  - 0005 put all eofblocks validation in xfs_fs_eofblocks_from_user()
>  - 0006 don't export internal flag, add K to internal flag name,
>    start internal flags bits at msb (with the intention that other internal
>    flags would be in descending order) and ensure that it doesn't accidentally
>    collide with external flags
> 
> Changes since v4 patchset (addressing Dave's comments):
>  - add parenthesis in if with binary and logical and (EOFBLOCKS flags)
>  - rename xfs_fs_eofblocks_to_internal -> xfs_fs_eofblocks_from_user and
>    move conversion validation into it
>  - fix negative error returns from XFS_IOC_FREE_EOFBLOCKS
>  - add check for read-only filesystem to XFS_IOC_FREE_EOFBLOCKS
> 
> Changes since v3 patchset:
>  - export inode_capable() for building xfs as a module
>  - implement Brian's proposal for an internal flag to indicate to
>    xfs_inode_free_eofblocks() that it should do a permission check.
>    ioctl callers will always set this flag, which is simpler than
>    making them specify XFS_EOF_FLAGS_UID or XFS_EOF_FLAGS_GID,
>    internal callers can leave it unset so no permission checking is
>    done
>  - take Brian's suggestion on moving the policy from the conversion
>    function into the ioctl code, and moving stuff to xfs_icache.h
> 
> _______________________________________________
> xfs mailing list
> xfs@xxxxxxxxxxx
> http://oss.sgi.com/mailman/listinfo/xfs
> 

<Prev in Thread] Current Thread [Next in Thread>