summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorChristoph Hellwig <hch@infradead.org>2010-01-21 11:17:20 +0000
committerAlex Elder <aelder@sgi.com>2010-01-21 16:34:23 -0600
commit9b00f30762fe9f914eb6e03057a616ed63a4e8ca (patch)
tree11644521534de9828b17e028f0d9c5d960785720
parentbdfb04301fa5fdd95f219539a9a5b9663b1e5fc2 (diff)
downloadop-kernel-dev-9b00f30762fe9f914eb6e03057a616ed63a4e8ca.zip
op-kernel-dev-9b00f30762fe9f914eb6e03057a616ed63a4e8ca.tar.gz
xfs: quota limit statvfs available blocks
A "df" run on an NFS client of an exported XFS file system reports the wrong information for "available" blocks. When a block quota is enforced, the amount reported as free is limited by the quota, but the amount reported available is not (and should be). Reported-by: Guk-Bong, Kwon <gbkwon@gmail.com> Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Alex Elder <aelder@sgi.com>
-rw-r--r--fs/xfs/quota/xfs_qm_bhv.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/xfs/quota/xfs_qm_bhv.c b/fs/xfs/quota/xfs_qm_bhv.c
index a534663..97b410c 100644
--- a/fs/xfs/quota/xfs_qm_bhv.c
+++ b/fs/xfs/quota/xfs_qm_bhv.c
@@ -59,7 +59,7 @@ xfs_fill_statvfs_from_dquot(
be64_to_cpu(dp->d_blk_hardlimit);
if (limit && statp->f_blocks > limit) {
statp->f_blocks = limit;
- statp->f_bfree =
+ statp->f_bfree = statp->f_bavail =
(statp->f_blocks > be64_to_cpu(dp->d_bcount)) ?
(statp->f_blocks - be64_to_cpu(dp->d_bcount)) : 0;
}
OpenPOWER on IntegriCloud