From: Junxiao Bi <junxiao.bi@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] ocfs2: fix recursive locking deadlock
Date: Tue, 10 May 2016 14:10:43 +0800 [thread overview]
Message-ID: <57317B63.8060806@oracle.com> (raw)
In-Reply-To: <20160509225804.e4ba0fb054acb1d92fe3db44@linux-foundation.org>
On 05/10/2016 01:58 PM, Andrew Morton wrote:
> On Tue, 10 May 2016 12:53:41 +0800 Junxiao Bi <junxiao.bi@oracle.com> wrote:
>
>> These two patches is to fix recursive locking deadlock issues. As we
>> talked with Mark before, recursive locking is not allowed in ocfs2,
>> so these two patches fixes the deadlock issue with reverting back
>> patches to avoid recursive locking. Please review.
>
> 2-3 years old so I guess it isn't a huge issue. Did you consider
> backporting into -stable kernels?
>
We'd better do that. I reproduced every one in my test env.
Thanks,
Junxiao.
next prev parent reply other threads:[~2016-05-10 6:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 4:53 [Ocfs2-devel] ocfs2: fix recursive locking deadlock Junxiao Bi
2016-05-10 4:53 ` [Ocfs2-devel] [PATCH 1/2] ocfs2: revert using ocfs2_acl_chmod to avoid inode cluster lock hang Junxiao Bi
2016-05-10 4:53 ` [Ocfs2-devel] [PATCH 2/2] ocfs2: fix posix_acl_create deadlock Junxiao Bi
2016-05-10 5:58 ` [Ocfs2-devel] ocfs2: fix recursive locking deadlock Andrew Morton
2016-05-10 6:10 ` Junxiao Bi [this message]
2016-05-10 6:50 ` Andrew Morton
2016-05-14 16:56 ` Jeong Woo Seo
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=57317B63.8060806@oracle.com \
--to=junxiao.bi@oracle.com \
--cc=ocfs2-devel@oss.oracle.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).