diff options
author | Lukas Czerner <lczerner@redhat.com> | 2013-02-18 12:12:07 -0500 |
---|---|---|
committer | Theodore Ts'o <tytso@mit.edu> | 2013-02-18 12:12:07 -0500 |
commit | 1231b3a1eb5740192aeebf5344dd6d6da000febf (patch) | |
tree | 733c93fe690972f65322107e7c4841707242c3e9 /fs/nfsd/nfsfh.h | |
parent | 74cd15cd02708c7188581f279f33a98b2ae8d322 (diff) | |
download | linux-1231b3a1eb5740192aeebf5344dd6d6da000febf.tar.gz linux-1231b3a1eb5740192aeebf5344dd6d6da000febf.tar.bz2 linux-1231b3a1eb5740192aeebf5344dd6d6da000febf.zip |
ext4: fix xattr block allocation/release with bigalloc
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>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Reviewed-by: Eric Sandeen <sandeen@redhat.com>
Cc: stable@vger.kernel.org
Diffstat (limited to 'fs/nfsd/nfsfh.h')
0 files changed, 0 insertions, 0 deletions