linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sougata Santra <sougata@tuxera.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Christoph Hellwig <hch@lst.de>, <linux-fsdevel@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	Vyacheslav Dubeyko <slava@dubeyko.com>,
	"Joe Perches" <joe@perches.com>,
	Alexey Khoroshilov <khoroshilov@ispras.ru>
Subject: Re: [PATCH] hfsplus: fix concurrent acess of alloc_blocks
Date: Wed, 19 Feb 2014 11:36:42 +0200	[thread overview]
Message-ID: <1392802602.32597.2.camel@ultrabook> (raw)
In-Reply-To: <20140218140642.fdc6a406f22de69bdf73e66e@linux-foundation.org>

On Tue, 2014-02-18 at 14:06 -0800, Andrew Morton wrote:
> On Mon, 17 Feb 2014 14:20:47 +0200 Sougata Santra <sougata@tuxera.com> wrote:
> 
> > 
> > Concurrent access to alloc_blocks in hfsplus_inode_info is
> > protected by extents_lock mutex. This patch fixes two
> > instances where alloc_blocks modification was not protected
> > with this lock. This fixes possible allocation bitmap
> > corruption in race conditions while extending and truncating
> > files.
> > 
> > ...
> >
> > --- a/fs/hfsplus/extents.c
> > +++ b/fs/hfsplus/extents.c
> > @@ -498,11 +498,13 @@ int hfsplus_file_extend(struct inode *inode)
> >  			goto insert_extent;
> >  	}
> >  out:
> > -	mutex_unlock(&hip->extents_lock);
> >  	if (!res) {
> >  		hip->alloc_blocks += len;
> > +		mutex_unlock(&hip->extents_lock);
> >  		hfsplus_mark_inode_dirty(inode, HFSPLUS_I_ALLOC_DIRTY);
> > +		return 0;
> >  	}
> > +	mutex_unlock(&hip->extents_lock);
> >  	return res;
> >  
> 
> This looks OK.
> 
> > @@ -592,9 +594,9 @@ void hfsplus_file_truncate(struct inode *inode)
> >  		hfs_brec_remove(&fd);
> >  	}
> >  	hfs_find_exit(&fd);
> > -	mutex_unlock(&hip->extents_lock);
> >  
> >  	hip->alloc_blocks = blk_cnt;
> > +	mutex_unlock(&hip->extents_lock);
> >  out:
> >  	hip->phys_size = inode->i_size;
> >  	hip->fs_blocks = (inode->i_size + sb->s_blocksize - 1) >>
> 
> But this does not.  To provide locking for
> hfsplus_inode_info.alloc_blocks, we must take the lock *before* taking
> a local copy of ->alloc_blocks.
> 
> Please review:
> 
> --- a/fs/hfsplus/extents.c~hfsplus-fix-concurrent-acess-of-alloc_blocks-fix
> +++ a/fs/hfsplus/extents.c
> @@ -556,11 +556,13 @@ void hfsplus_file_truncate(struct inode
>  
>  	blk_cnt = (inode->i_size + HFSPLUS_SB(sb)->alloc_blksz - 1) >>
>  			HFSPLUS_SB(sb)->alloc_blksz_shift;
> +
> +	mutex_lock(&hip->extents_lock);
> +
>  	alloc_cnt = hip->alloc_blocks;
>  	if (blk_cnt == alloc_cnt)
> -		goto out;
> +		goto out_unlock;
>  
> -	mutex_lock(&hip->extents_lock);
>  	res = hfs_find_init(HFSPLUS_SB(sb)->ext_tree, &fd);
>  	if (res) {
>  		mutex_unlock(&hip->extents_lock);
> @@ -594,6 +596,7 @@ void hfsplus_file_truncate(struct inode
>  	hfs_find_exit(&fd);
>  
>  	hip->alloc_blocks = blk_cnt;
> +out_unlock:
>  	mutex_unlock(&hip->extents_lock);
>  out:
>  	hip->phys_size = inode->i_size;
> _
> 
This is good, Missed it. Thank you.

  reply	other threads:[~2014-02-19  9:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-17 12:20 [PATCH] hfsplus: fix concurrent acess of alloc_blocks Sougata Santra
2014-02-18 22:06 ` Andrew Morton
2014-02-19  9:36   ` Sougata Santra [this message]
2014-02-19  9:53   ` sougata santra

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=1392802602.32597.2.camel@ultrabook \
    --to=sougata@tuxera.com \
    --cc=akpm@linux-foundation.org \
    --cc=hch@lst.de \
    --cc=joe@perches.com \
    --cc=khoroshilov@ispras.ru \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=slava@dubeyko.com \
    /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).