linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Li Xi <pkuelelixi@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
	linux-api@vger.kernel.org, tytso@mit.edu, adilger@dilger.ca,
	jack@suse.cz, viro@zeniv.linux.org.uk, hch@infradead.org,
	dmonakhov@openvz.org, dchinner@redhat.com
Subject: Re: [v9 1/5] vfs: adds general codes to enforces project quota limits
Date: Mon, 16 Mar 2015 15:29:44 +0100	[thread overview]
Message-ID: <20150316142944.GN4934@quack.suse.cz> (raw)
In-Reply-To: <1426043003-31043-2-git-send-email-lixi@ddn.com>

On Wed 11-03-15 12:03:19, Li Xi wrote:
> This patch adds support for a new quota type PRJQUOTA for project quota
> enforcement. Also a new method get_projid() is added into dquot_operations
> structure.
> 
> Signed-off-by: Li Xi <lixi@ddn.com>
> Signed-off-by: Dmitry Monakhov <dmonakhov@openvz.org>
> Reviewed-by: Jan Kara <jack@suse.cz>
...
> diff --git a/fs/quota/quota.c b/fs/quota/quota.c
> index 2aa4151..c76b350 100644
> --- a/fs/quota/quota.c
> +++ b/fs/quota/quota.c
> @@ -30,11 +30,15 @@ static int check_quotactl_permission(struct super_block *sb, int type, int cmd,
>  	case Q_XGETQSTATV:
>  	case Q_XQUOTASYNC:
>  		break;
> -	/* allow to query information for dquots we "own" */
> +	/*
> +	 * allow to query information for dquots we "own"
> +	 * always allow querying project quota
> +	 */
>  	case Q_GETQUOTA:
>  	case Q_XGETQUOTA:
>  		if ((type == USRQUOTA && uid_eq(current_euid(), make_kuid(current_user_ns(), id))) ||
> -		    (type == GRPQUOTA && in_egroup_p(make_kgid(current_user_ns(), id))))
> +		    (type == GRPQUOTA && in_egroup_p(make_kgid(current_user_ns(), id))) ||
> +		    (type == PRJQUOTA))
>  			break;
  I wanted to merge this patch but this hunk caught my eye. Why do we
suddently allow querying of project quotas? Traditionally that has been
allowed only with CAP_SYS_ADMIN. I agree it looks too restrictive to me but
unless that's a bug, I think we have to adhere to original behavior and
drop this hunk. Dave, was that behavior of project quotas intended? 

								Honza
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

  reply	other threads:[~2015-03-16 14:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-11  3:03 [v9 0/5] ext4: add project quota support Li Xi
2015-03-11  3:03 ` [v9 2/5] ext4: adds project ID support Li Xi
     [not found]   ` <1426043003-31043-3-git-send-email-lixi-LfVdkaOWEx8@public.gmane.org>
2015-03-16 14:37     ` Jan Kara
     [not found] ` <1426043003-31043-1-git-send-email-lixi-LfVdkaOWEx8@public.gmane.org>
2015-03-11  3:03   ` [v9 1/5] vfs: adds general codes to enforces project quota limits Li Xi
2015-03-16 14:29     ` Jan Kara [this message]
2015-03-16 21:49       ` Dave Chinner
2015-03-17  9:37         ` Jan Kara
2015-03-11  3:03   ` [v9 3/5] ext4: adds project quota support Li Xi
     [not found]     ` <1426043003-31043-4-git-send-email-lixi-LfVdkaOWEx8@public.gmane.org>
2015-03-11  7:40       ` Konstantin Khlebnikov
2015-03-12 15:01         ` Andreas Dilger
2015-03-12 16:04           ` Konstantin Khlebnikov
2015-03-16 14:47           ` Jan Kara
2015-03-16 14:57             ` Konstantin Khlebnikov
2015-03-16 15:33               ` Jan Kara
2015-03-11  3:03   ` [v9 4/5] ext4: adds FS_IOC_FSSETXATTR/FS_IOC_FSGETXATTR interface support Li Xi
     [not found]     ` <1426043003-31043-5-git-send-email-lixi-LfVdkaOWEx8@public.gmane.org>
2015-03-11  7:33       ` Konstantin Khlebnikov
2015-03-16 15:26       ` Jan Kara
2015-03-11  3:03 ` [v9 5/5] ext4: cleanup inode flag definitions Li Xi

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=20150316142944.GN4934@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=adilger@dilger.ca \
    --cc=dchinner@redhat.com \
    --cc=dmonakhov@openvz.org \
    --cc=hch@infradead.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=pkuelelixi@gmail.com \
    --cc=tytso@mit.edu \
    --cc=viro@zeniv.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).