From: Eric Sandeen <sandeen@redhat.com>
To: Lukas Czerner <lczerner@redhat.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: fix xattr block allocation/release with bigalloc
Date: Mon, 18 Feb 2013 09:26:07 -0600 [thread overview]
Message-ID: <5122480F.9030100@redhat.com> (raw)
In-Reply-To: <1361175262-16205-1-git-send-email-lczerner@redhat.com>
On 2/18/13 2:14 AM, Lukas Czerner wrote:
> Currently when new xattr block is created or released we we would call
> dquot_free_block() or dquot_alloc_block() respectively, among the else
> decrementing or incrementing the number of blocks assigned to the inode
> by one block.
>
> This however does not work for bigalloc file system because we always
> allocate/free the whole cluster so we have to count with that in
> dquot_free_block() and dquot_alloc_block() as well.
>
> Use the clusters-to-blocks conversion EXT4_C2B() when passing number of
> blocks to the dquot_alloc/free functions to fix the problem.
>
> The problem has been revealed by xfstests #117 (and possibly others).
>
> Signed-off-by: Lukas Czerner <lczerner@redhat.com>
Thanks for finding this!
Reviewed-by: Eric Sandeen <sandeen@redhat.com>
> ---
> fs/ext4/xattr.c | 7 ++++---
> 1 files changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/fs/ext4/xattr.c b/fs/ext4/xattr.c
> index 3a91ebc..b6741be 100644
> --- a/fs/ext4/xattr.c
> +++ b/fs/ext4/xattr.c
> @@ -549,7 +549,7 @@ ext4_xattr_release_block(handle_t *handle, struct inode *inode,
> error = ext4_handle_dirty_xattr_block(handle, inode, bh);
> if (IS_SYNC(inode))
> ext4_handle_sync(handle);
> - dquot_free_block(inode, 1);
> + dquot_free_block(inode, EXT4_C2B(EXT4_SB(inode->i_sb), 1));
> ea_bdebug(bh, "refcount now=%d; releasing",
> le32_to_cpu(BHDR(bh)->h_refcount));
> }
> @@ -832,7 +832,8 @@ inserted:
> else {
> /* The old block is released after updating
> the inode. */
> - error = dquot_alloc_block(inode, 1);
> + error = dquot_alloc_block(inode,
> + EXT4_C2B(EXT4_SB(sb), 1));
> if (error)
> goto cleanup;
> error = ext4_journal_get_write_access(handle,
> @@ -928,7 +929,7 @@ cleanup:
> return error;
>
> cleanup_dquot:
> - dquot_free_block(inode, 1);
> + dquot_free_block(inode, EXT4_C2B(EXT4_SB(sb), 1));
> goto cleanup;
>
> bad_block:
>
next prev parent reply other threads:[~2013-02-18 15:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 8:14 [PATCH] ext4: fix xattr block allocation/release with bigalloc Lukas Czerner
2013-02-18 15:26 ` Eric Sandeen [this message]
2013-02-18 17:25 ` Theodore Ts'o
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=5122480F.9030100@redhat.com \
--to=sandeen@redhat.com \
--cc=lczerner@redhat.com \
--cc=linux-ext4@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).