xfs: report proper f_files in statfs if we overshoot imaxpct
authorEric Sandeen <sandeen@redhat.com>
Thu, 5 Feb 2015 22:53:02 +0000 (09:53 +1100)
committerDave Chinner <david@fromorbit.com>
Thu, 5 Feb 2015 22:53:02 +0000 (09:53 +1100)
commit01f9882eac84b85421a469cb65ee9bb555a5985f
tree9d2903b03f8923d93db1f6408231254ec5c3514b
parentde8bd0eb699e6f20e2e2ce368fe35aa83732718b
xfs: report proper f_files in statfs if we overshoot imaxpct

Normally, a statfs syscall reports m_maxicount as f_files
(total file nodes in file system) because it is supposed
to be the upper limit for dynamically-allocated inodes.

It's possible, however, to overshoot imaxpct / m_maxicount.
If this happens, we should report the actual number of allocated
inodes, which is contained in sb_icount.  Add one more adjustment
to the statfs code to make this happen.

Reported-by: Alexander Tsvetkov <alexander.tsvetkov@oracle.com>
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Reviewed-by: Dave Chinner <dchinner@redhat.com>
Signed-off-by: Dave Chinner <david@fromorbit.com>
fs/xfs/xfs_super.c