From: Goldwyn Rodrigues <rgoldwyn@suse.de>
To: linux-fsdevel@vger.kernel.org
Cc: linux-mm@kvack.org, willy@infradead.org, david@fromorbit.com,
Goldwyn Rodrigues <rgoldwyn@suse.com>
Subject: [PATCH 1/3] fs: Perform writebacks under memalloc_nofs
Date: Wed, 21 Mar 2018 17:44:27 -0500 [thread overview]
Message-ID: <20180321224429.15860-2-rgoldwyn@suse.de> (raw)
In-Reply-To: <20180321224429.15860-1-rgoldwyn@suse.de>
From: Goldwyn Rodrigues <rgoldwyn@suse.com>
writebacks can recurse into itself under low memory situations.
Set memalloc_nofs_save() in order to make sure it does not
recurse.
Since writeouts are performed for fdatawrites as well, set
memalloc_nofs_save while performing fdatawrites.
Signed-off-by: Goldwyn Rodrigues <rgoldwyn@suse.com>
---
fs/fs-writeback.c | 8 ++++++++
fs/xfs/xfs_aops.c | 7 -------
mm/filemap.c | 3 +++
3 files changed, 11 insertions(+), 7 deletions(-)
diff --git a/fs/fs-writeback.c b/fs/fs-writeback.c
index d4d04fee568a..42f7f4c2063b 100644
--- a/fs/fs-writeback.c
+++ b/fs/fs-writeback.c
@@ -28,6 +28,7 @@
#include <linux/tracepoint.h>
#include <linux/device.h>
#include <linux/memcontrol.h>
+#include <linux/sched/mm.h>
#include "internal.h"
/*
@@ -1713,7 +1714,12 @@ static long wb_writeback(struct bdi_writeback *wb,
struct inode *inode;
long progress;
struct blk_plug plug;
+ unsigned flags;
+ if (current->flags & PF_MEMALLOC_NOFS)
+ return 0;
+
+ flags = memalloc_nofs_save();
oldest_jif = jiffies;
work->older_than_this = &oldest_jif;
@@ -1797,6 +1803,8 @@ static long wb_writeback(struct bdi_writeback *wb,
spin_unlock(&wb->list_lock);
blk_finish_plug(&plug);
+ memalloc_nofs_restore(flags);
+
return nr_pages - work->nr_pages;
}
diff --git a/fs/xfs/xfs_aops.c b/fs/xfs/xfs_aops.c
index 9c6a830da0ee..943ade03489a 100644
--- a/fs/xfs/xfs_aops.c
+++ b/fs/xfs/xfs_aops.c
@@ -1086,13 +1086,6 @@ xfs_do_writepage(
PF_MEMALLOC))
goto redirty;
- /*
- * Given that we do not allow direct reclaim to call us, we should
- * never be called while in a filesystem transaction.
- */
- if (WARN_ON_ONCE(current->flags & PF_MEMALLOC_NOFS))
- goto redirty;
-
/*
* Is this page beyond the end of the file?
*
diff --git a/mm/filemap.c b/mm/filemap.c
index 693f62212a59..3c9ead9a1e32 100644
--- a/mm/filemap.c
+++ b/mm/filemap.c
@@ -430,6 +430,7 @@ int __filemap_fdatawrite_range(struct address_space *mapping, loff_t start,
loff_t end, int sync_mode)
{
int ret;
+ unsigned flags;
struct writeback_control wbc = {
.sync_mode = sync_mode,
.nr_to_write = LONG_MAX,
@@ -440,9 +441,11 @@ int __filemap_fdatawrite_range(struct address_space *mapping, loff_t start,
if (!mapping_cap_writeback_dirty(mapping))
return 0;
+ flags = memalloc_nofs_save();
wbc_attach_fdatawrite_inode(&wbc, mapping->host);
ret = do_writepages(mapping, &wbc);
wbc_detach_inode(&wbc);
+ memalloc_nofs_restore(flags);
return ret;
}
--
2.16.2
next prev parent reply other threads:[~2018-03-21 22:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 22:44 [PATCH 0/3] fs: Use memalloc_nofs_save/restore scope API Goldwyn Rodrigues
2018-03-21 22:44 ` Goldwyn Rodrigues [this message]
2018-03-22 7:08 ` [PATCH 1/3] fs: Perform writebacks under memalloc_nofs Michal Hocko
2018-03-27 12:52 ` Goldwyn Rodrigues
2018-03-27 14:21 ` Matthew Wilcox
2018-03-27 15:13 ` Goldwyn Rodrigues
2018-03-27 16:45 ` Matthew Wilcox
2018-03-28 7:01 ` Michal Hocko
2018-03-28 23:57 ` Dave Chinner
2018-03-29 7:01 ` Michal Hocko
2018-03-31 21:21 ` Dave Chinner
2018-03-21 22:44 ` [PATCH 2/3] fs: use memalloc_nofs API while shrinking superblock Goldwyn Rodrigues
2018-03-22 7:09 ` Michal Hocko
2018-03-21 22:44 ` [PATCH 3/3] fs: Use memalloc_nofs_save in generic_perform_write Goldwyn Rodrigues
2018-03-22 7:10 ` Michal Hocko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180321224429.15860-2-rgoldwyn@suse.de \
--to=rgoldwyn@suse.de \
--cc=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rgoldwyn@suse.com \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).