linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: Jan Kara <jack@suse.cz>, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 5/5] quota: handle IO errors in dquot_transfer()
Date: Mon, 14 Dec 2009 19:41:28 +0100	[thread overview]
Message-ID: <20091214184127.GH4731@quack.suse.cz> (raw)
In-Reply-To: <1260793276-8511-5-git-send-email-dmonakhov@openvz.org>

On Mon 14-12-09 15:21:16, Dmitry Monakhov wrote:
> transfer_to[cnt] = dqget() may returns NULL due to IO error.
> But NULL value in transfer_to[cnt] means a dquot transfer
> optimization. So after operation succeed inode will have new
> i_uid or i_gid but accounted to old dquot. This behaviour
> is differ from dquot_initialize(). Let's handle IO error from
> dqget() equally in all functions.
> 
> In appliance to dquot_transfer() this means that we have to finish
> operation regardless to IO errors from dqget().
  In principle, the patch is fine (see just about a bug below). But even
better would be if you converted dquot_transfer() to actually return real
return codes (0, -EDQUOT, -EIO...) and make it return EIO in case of IO
error. Then a filesystem can properly fail chown if quota transfer cannot
be performed. This is a larger project since filesystems using
dquot_transfer need to be changed and also other dquot_... functions need
to be converted to this calling convention for the sake of consistency. But
it would be a good cleanup.

...
>  	for (cnt = 0; cnt < MAXQUOTAS; cnt++) {
> -		transfer_from[cnt] = NULL;
> -		transfer_to[cnt] = NULL;
>  		warntype_to[cnt] = QUOTA_NL_NOWARN;
> +		if (!valid[cnt])
> +			continue;
> +		transfer_to[cnt] = dqget(inode->i_sb, iattr->ia_uid, cnt);
  This is wrong! You have to take ia_gid in case of GRPQUOTA.

> @@ -1767,9 +1769,11 @@ int dquot_transfer(struct inode *inode, struct iattr *iattr)
>  	space = cur_space + rsv_space;
>  	/* Build the transfer_from list and check the limits */
>  	for (cnt = 0; cnt < MAXQUOTAS; cnt++) {
> -		if (!transfer_to[cnt])
> +		if (!valid[cnt])
>  			continue;
>  		transfer_from[cnt] = inode->i_dquot[cnt];
> +		if (!transfer_to[cnt])
> +			continue;
>  		if (check_idq(transfer_to[cnt], 1, warntype_to + cnt) ==
>  		    NO_QUOTA || check_bdq(transfer_to[cnt], space, 0,
>  		    warntype_to + cnt) == NO_QUOTA)
> @@ -1783,10 +1787,15 @@ int dquot_transfer(struct inode *inode, struct iattr *iattr)
>  		/*
>  		 * Skip changes for same uid or gid or for turned off quota-type.
>  		 */
> -		if (!transfer_to[cnt])
> +		if (!valid[cnt])
>  			continue;
> +		/*
> +		 * Due to IO error we might not have transfer_to[] or
> +		 * transfer_from[] structure. Nor than less the operation must
                                              ^^ I suppose this should be
"Nonetheless"
> +		 * being done regardless quota io errors.
> +		 */
> +		inode->i_dquot[cnt] = transfer_to[cnt];
>  
> -		/* Due to IO error we might not have transfer_from[] structure */
>  		if (transfer_from[cnt]) {
>  			warntype_from_inodes[cnt] =
>  				info_idq_free(transfer_from[cnt], 1);
> @@ -1797,12 +1806,11 @@ int dquot_transfer(struct inode *inode, struct iattr *iattr)
>  			dquot_free_reserved_space(transfer_from[cnt],
>  						  rsv_space);
>  		}
> -
> -		dquot_incr_inodes(transfer_to[cnt], 1);
> -		dquot_incr_space(transfer_to[cnt], cur_space);
> -		dquot_resv_space(transfer_to[cnt], rsv_space);
> -
> -		inode->i_dquot[cnt] = transfer_to[cnt];
> +		if (transfer_to[cnt]) {
> +			dquot_incr_inodes(transfer_to[cnt], 1);
> +			dquot_incr_space(transfer_to[cnt], cur_space);
> +			dquot_resv_space(transfer_to[cnt], rsv_space);
> +		}
>  	}
>  	spin_unlock(&dq_data_lock);
>  	up_write(&sb_dqopt(inode->i_sb)->dqptr_sem);
> -- 
> 1.6.0.4
> 
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

  reply	other threads:[~2009-12-14 18:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-14 12:21 [PATCH 1/5] Add unlocked version of inode_add_bytes() function Dmitry Monakhov
2009-12-14 12:21 ` [PATCH 2/5] quota: decouple fs reserved space from quota reservation. [V5] Dmitry Monakhov
2009-12-14 12:21   ` [PATCH 3/5] ext4: Convert to generic reserved quota's space management. [V5] Dmitry Monakhov
2009-12-14 12:21     ` [PATCH 4/5] quota: Move duplicated code to separate functions Dmitry Monakhov
2009-12-14 12:21       ` [PATCH 5/5] quota: handle IO errors in dquot_transfer() Dmitry Monakhov
2009-12-14 18:41         ` Jan Kara [this message]
2009-12-14 22:43           ` Dmitry Monakhov
2009-12-15 11:49             ` Jan Kara
2009-12-14 18:00       ` [PATCH 4/5] quota: Move duplicated code to separate functions Jan Kara
2009-12-14 14:35     ` [PATCH 3/5] ext4: Convert to generic reserved quota's space management. [V5] tytso
2009-12-14 17:26       ` Jan Kara
2009-12-14 17:25     ` Jan Kara
2009-12-14 17:24   ` [PATCH 2/5] quota: decouple fs reserved space from quota reservation. [V5] Jan Kara
2009-12-14 17:21 ` [PATCH 1/5] Add unlocked version of inode_add_bytes() function Jan Kara

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=20091214184127.GH4731@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=dmonakhov@openvz.org \
    --cc=linux-fsdevel@vger.kernel.org \
    /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).