gfs2: forcibly flush ail to relieve memory pressure
authorAbhi Das <adas@redhat.com>
Fri, 4 Aug 2017 17:15:32 +0000 (12:15 -0500)
committerBob Peterson <rpeterso@redhat.com>
Thu, 10 Aug 2017 15:51:03 +0000 (10:51 -0500)
commitb066a4eebd4f5ea77f7e5c7d13104d38e1a1d4bf
treeb8f53940b11052f2cb444f21586063eed0c1f3e5
parenta91323e255fa8bc84b0acf63376b395c534a38fa
gfs2: forcibly flush ail to relieve memory pressure

On systems with low memory, it is possible for gfs2 to infinitely
loop in balance_dirty_pages() under heavy IO (creating sparse files).

balance_dirty_pages() attempts to write out the dirty pages via
gfs2_writepages() but none are found because these dirty pages are
being used by the journaling code in the ail. Normally, the journal
has an upper threshold which when hit triggers an automatic flush
of the ail. But this threshold can be higher than the number of
allowable dirty pages and result in the ail never being flushed.

This patch forces an ail flush when gfs2_writepages() fails to write
anything. This is a good indication that the ail might be holding
some dirty pages.

Signed-off-by: Abhi Das <adas@redhat.com>
Signed-off-by: Bob Peterson <rpeterso@redhat.com>
fs/gfs2/aops.c
fs/gfs2/incore.h
fs/gfs2/log.c