aboutsummaryrefslogtreecommitdiff
path: root/crypto
diff options
context:
space:
mode:
authorDave Chinner <david@fromorbit.com>2010-01-02 02:39:40 +0000
committerAlex Elder <aelder@sgi.com>2010-01-10 12:22:00 -0600
commit44e08c45cc14e6190a424be8d450070c8e508fad (patch)
treef0938a953d0bce87cade91ec753293c305925296 /crypto
parentd6d59bada372bcf8bd36c3bbc71c485c29dd2a4b (diff)
xfs: Don't flush stale inodes
Because inodes remain in cache much longer than inode buffers do under memory pressure, we can get the situation where we have stale, dirty inodes being reclaimed but the backing storage has been freed. Hence we should never, ever flush XFS_ISTALE inodes to disk as there is no guarantee that the backing buffer is in cache and still marked stale when the flush occurs. Signed-off-by: Dave Chinner <david@fromorbit.com> Signed-off-by: Alex Elder <aelder@sgi.com>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions