aboutsummaryrefslogtreecommitdiff
path: root/lib/memory-notifier-error-inject.c
diff options
context:
space:
mode:
authorEric Sandeen <[email protected]>2015-02-06 09:53:02 +1100
committerDave Chinner <[email protected]>2015-02-06 09:53:02 +1100
commit01f9882eac84b85421a469cb65ee9bb555a5985f (patch)
tree9d2903b03f8923d93db1f6408231254ec5c3514b /lib/memory-notifier-error-inject.c
parentde8bd0eb699e6f20e2e2ce368fe35aa83732718b (diff)
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 <[email protected]> Signed-off-by: Eric Sandeen <[email protected]> Reviewed-by: Dave Chinner <[email protected]> Signed-off-by: Dave Chinner <[email protected]>
Diffstat (limited to 'lib/memory-notifier-error-inject.c')
0 files changed, 0 insertions, 0 deletions