[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1483630262-22227-1-git-send-email-zren@suse.com>
Date: Thu, 5 Jan 2017 23:31:00 +0800
From: Eric Ren <zren@...e.com>
To: ocfs2-devel@....oracle.com
Cc: akpm@...ux-foundation.org, mfasheh@...sity.com, jlbec@...lplan.org,
ghe@...e.com, junxiao.bi@...cle.com, jiangqi903@...il.com,
zren@...e.com, linux-kernel@...r.kernel.org
Subject: [PATCH 0/2] fix deadlock caused by recursive cluster locking
This is a formal patch set to solve the deadlock issue on which I
previously started a RFC (draft patch), and the discussion happened here:
[https://oss.oracle.com/pipermail/ocfs2-devel/2016-October/012455.html]
Compared to the previous draft patch, this one is much simple and neat.
It neither messes up the dlmglue core, nor has a performance penalty on
the whole cluster locking system. Instead, it is only used in places where
such recursive cluster locking may happen.
Your comments and feedbacks are always welcomed.
Eric Ren (2):
ocfs2/dlmglue: prepare tracking logic to avoid recursive cluster lock
ocfs2: fix deadlocks when taking inode lock at vfs entry points
fs/ocfs2/acl.c | 39 ++++++++++++++++++++++++++++++++++-----
fs/ocfs2/dlmglue.c | 47 ++++++++++++++++++++++++++++++++++++++++++++---
fs/ocfs2/dlmglue.h | 18 ++++++++++++++++++
fs/ocfs2/file.c | 44 ++++++++++++++++++++++++++++++++++----------
fs/ocfs2/ocfs2.h | 1 +
5 files changed, 131 insertions(+), 18 deletions(-)
--
2.6.6
Powered by blists - more mailing lists