From: Andreas Gruenbacher <agruenba@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH v3 4/4] gfs2: Defer deleting inodes under memory pressure
Date: Tue, 1 Aug 2017 02:00:22 +0200 [thread overview]
Message-ID: <20170801000022.13295-5-agruenba@redhat.com> (raw)
In-Reply-To: <20170801000022.13295-1-agruenba@redhat.com>
When under memory pressure and an inode's link count has dropped to
zero, defer deleting the inode to the delete workqueue. This avoids
calling into DLM under memory pressure, which can deadlock.
Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>
---
fs/gfs2/super.c | 23 +++++++++++++++++++++++
1 file changed, 23 insertions(+)
diff --git a/fs/gfs2/super.c b/fs/gfs2/super.c
index 027abb11337b..958a2c5eec2a 100644
--- a/fs/gfs2/super.c
+++ b/fs/gfs2/super.c
@@ -1318,6 +1318,25 @@ static int gfs2_drop_inode(struct inode *inode)
if (test_bit(GLF_DEMOTE, &gl->gl_flags))
clear_nlink(inode);
}
+
+ /*
+ * When under memory pressure when an inode's link count has dropped to
+ * zero, defer deleting the inode to the delete workqueue. This avoids
+ * calling into DLM under memory pressure, which can deadlock.
+ */
+ if (!inode->i_nlink &&
+ unlikely(current->flags & PF_MEMALLOC) &&
+ gfs2_holder_initialized(&ip->i_iopen_gh)) {
+ struct gfs2_glock *gl = ip->i_iopen_gh.gh_gl;
+
+ spin_lock(&gl->gl_lockref.lock);
+ gl->gl_lockref.count++;
+ if (queue_work(gfs2_delete_workqueue, &gl->gl_delete) == 0)
+ gl->gl_lockref.count--;
+ spin_unlock(&gl->gl_lockref.lock);
+ return false;
+ }
+
return generic_drop_inode(inode);
}
@@ -1545,6 +1564,10 @@ static void gfs2_evict_inode(struct inode *inode)
goto alloc_failed;
}
+ /* Deletes should never happen under memory pressure anymore. */
+ if (WARN_ON_ONCE(current->flags & PF_MEMALLOC))
+ goto out;
+
/* Must not read inode block until block type has been verified */
error = gfs2_glock_nq_init(ip->i_gl, LM_ST_EXCLUSIVE, GL_SKIP, &gh);
if (unlikely(error)) {
--
2.13.3
next prev parent reply other threads:[~2017-08-01 0:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 0:00 [Cluster-devel] [PATCH v3 0/4] GFS2 shrinker deadlock Andreas Gruenbacher
2017-08-01 0:00 ` [Cluster-devel] [PATCH v3 1/4] gfs2: gfs2_glock_get: Wait on freeing glocks Andreas Gruenbacher
2017-08-03 12:04 ` Andrew Price
2017-08-01 0:00 ` [Cluster-devel] [PATCH v3 2/4] gfs2: Get rid of gfs2_set_nlink Andreas Gruenbacher
2017-08-01 0:00 ` [Cluster-devel] [PATCH v3 3/4] gfs2: gfs2_evict_inode: Put glocks asynchronously Andreas Gruenbacher
2017-08-01 0:00 ` Andreas Gruenbacher [this message]
2017-08-01 17:00 ` [Cluster-devel] [PATCH v3 0/4] GFS2 shrinker deadlock Bob Peterson
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=20170801000022.13295-5-agruenba@redhat.com \
--to=agruenba@redhat.com \
/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).