linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Andrew Perepechko <Andrew.Perepechko@Sun.COM>
Cc: jack@suse.cz, Johann Lombardi <johann@Sun.COM>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 01/01] quota: atomic dq_flags operations in do_set_dqblk
Date: Mon, 12 Apr 2010 21:09:17 +0200	[thread overview]
Message-ID: <20100412190914.GL3404@quack.suse.cz> (raw)
In-Reply-To: <201004122216.50365.andrew.perepechko@sun.com>

On Mon 12-04-10 22:16:50, Andrew Perepechko wrote:
> From: Andrew Perepechko <andrew.perepechko@sun.com>
> 
> Non-atomic __set_bit calls are replaced with atomic set_bit calls in do_set_dqblk
> so that individual bits should not be lost in a possible race condition.
  I took a liberty of modifying the changelog to be more descriptive:

quota: Fix possible dq_flags corruption
    
dq_flags are modified non-atomically in do_set_dqblk via __set_bit calls
and atomically for example in mark_dquot_dirty or clear_dquot_dirty.  Hence
a change done by an atomic operation can be overwritten by a change done by
a non-atomic one. Fix the problem by using atomic bitops even in
do_set_dqblk.

  Otherwise I've merged the patch.

								Honza

> Signed-off-by: Andrew Perepechko <andrew.perepechko@sun.com>
> ---
> diff -puN fs/dquot.c fs/dquot.c
> --- a/fs/dquot.c
> +++ b/fs/dquot.c
> @@ -2065,32 +2065,32 @@ static int do_set_dqblk(struct dquot *dq
>  	if (di->dqb_valid & QIF_SPACE) {
>  		dm->dqb_curspace = di->dqb_curspace;
>  		check_blim = 1;
> -		__set_bit(DQ_LASTSET_B + QIF_SPACE_B, &dquot->dq_flags);
> +		set_bit(DQ_LASTSET_B + QIF_SPACE_B, &dquot->dq_flags);
>  	}
>  	if (di->dqb_valid & QIF_BLIMITS) {
>  		dm->dqb_bsoftlimit = qbtos(di->dqb_bsoftlimit);
>  		dm->dqb_bhardlimit = qbtos(di->dqb_bhardlimit);
>  		check_blim = 1;
> -		__set_bit(DQ_LASTSET_B + QIF_BLIMITS_B, &dquot->dq_flags);
> +		set_bit(DQ_LASTSET_B + QIF_BLIMITS_B, &dquot->dq_flags);
>  	}
>  	if (di->dqb_valid & QIF_INODES) {
>  		dm->dqb_curinodes = di->dqb_curinodes;
>  		check_ilim = 1;
> -		__set_bit(DQ_LASTSET_B + QIF_INODES_B, &dquot->dq_flags);
> +		set_bit(DQ_LASTSET_B + QIF_INODES_B, &dquot->dq_flags);
>  	}
>  	if (di->dqb_valid & QIF_ILIMITS) {
>  		dm->dqb_isoftlimit = di->dqb_isoftlimit;
>  		dm->dqb_ihardlimit = di->dqb_ihardlimit;
>  		check_ilim = 1;
> -		__set_bit(DQ_LASTSET_B + QIF_ILIMITS_B, &dquot->dq_flags);
> +		set_bit(DQ_LASTSET_B + QIF_ILIMITS_B, &dquot->dq_flags);
>  	}
>  	if (di->dqb_valid & QIF_BTIME) {
>  		dm->dqb_btime = di->dqb_btime;
> -		__set_bit(DQ_LASTSET_B + QIF_BTIME_B, &dquot->dq_flags);
> +		set_bit(DQ_LASTSET_B + QIF_BTIME_B, &dquot->dq_flags);
>  	}
>  	if (di->dqb_valid & QIF_ITIME) {
>  		dm->dqb_itime = di->dqb_itime;
> -		__set_bit(DQ_LASTSET_B + QIF_ITIME_B, &dquot->dq_flags);
> +		set_bit(DQ_LASTSET_B + QIF_ITIME_B, &dquot->dq_flags);
>  	}
>  
>  	if (check_blim) {
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

  reply	other threads:[~2010-04-12 19:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-12 18:16 [PATCH 01/01] quota: atomic dq_flags operations in do_set_dqblk Andrew Perepechko
2010-04-12 19:09 ` Jan Kara [this message]
2010-04-12 19:39   ` Andrew Perepechko

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=20100412190914.GL3404@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=Andrew.Perepechko@Sun.COM \
    --cc=johann@Sun.COM \
    --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).