From: piaojun <piaojun@huawei.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [DRAFT 2/2] ocfs2: fix deadlock caused by recursive cluster locking
Date: Mon, 14 Nov 2016 13:42:58 +0800 [thread overview]
Message-ID: <58294EE2.1000900@huawei.com> (raw)
In-Reply-To: <968237e5-b308-84cc-2c99-637cdd13bd4c@suse.com>
Hi Eric,
On 2016-11-11 9:56, Eric Ren wrote:
> Hi,
>
> On 11/10/2016 06:49 PM, piaojun wrote:
>> Hi Eric,
>>
>> On 2016-11-1 9:45, Eric Ren wrote:
>>> Hi,
>>>
>>> On 10/31/2016 06:55 PM, piaojun wrote:
>>>> Hi Eric,
>>>>
>>>> On 2016-10-19 13:19, Eric Ren wrote:
>>>>> The deadlock issue happens when running discontiguous block
>>>>> group testing on multiple nodes. The easier way to reproduce
>>>>> is to do "chmod -R 777 /mnt/ocfs2" things like this on multiple
>>>>> nodes at the same time by pssh.
>>>>>
>>>>> This is indeed another deadlock caused by: commit 743b5f1434f5
>>>>> ("ocfs2: take inode lock in ocfs2_iop_set/get_acl()"). The reason
>>>>> had been explained well by Tariq Saeed in this thread:
>>>>>
>>>>> https://oss.oracle.com/pipermail/ocfs2-devel/2015-September/011085.html
>>>>>
>>>>> For this case, the ocfs2_inode_lock() is misused recursively as below:
>>>>>
>>>>> do_sys_open
>>>>> do_filp_open
>>>>> path_openat
>>>>> may_open
>>>>> inode_permission
>>>>> __inode_permission
>>>>> ocfs2_permission <====== ocfs2_inode_lock()
>>>>> generic_permission
>>>>> get_acl
>>>>> ocfs2_iop_get_acl <====== ocfs2_inode_lock()
>>>>> ocfs2_inode_lock_full_nested <===== deadlock if a remote EX request
>>>> Do you mean another node wants to get ex of the inode? or another process?
>>> Remote EX request means "another node wants to get ex of the inode";-)
>>>
>>> Eric
>> If another node wants to get ex, it will get blocked as this node has
>> got pr. Why will the ex request make this node get blocked? Expect your
>> detailed description.
> Did you look at this link I mentioned above?
>
> OCFS2_LOCK_BLOCKED flag of this lockres is set in BAST (ocfs2_generic_handle_bast) when downconvert is needed
> on behalf of remote lock request.
>
> The recursive cluster lock (the second one) will be blocked in __ocfs2_cluster_lock() because of OCFS2_LOCK_BLOCKED.
> But the downconvert cannot be done, why? because there is no chance for the first cluster lock on this node to be unlocked -
> we blocked ourselves in the code path.
>
> Eric
You clear my doubt. I will look through your solution.
thanks
Jun
>>
>> thanks,
>> Jun
>>>>> comes between two ocfs2_inode_lock()
>>>>>
>>>>> Fix by checking if the cluster lock has been acquired aready in the call-chain
>>>>> path.
>>>>>
>>>>> Fixes: commit 743b5f1434f5 ("ocfs2: take inode lock in ocfs2_iop_set/get_acl()")
>>>>> Signed-off-by: Eric Ren <zren@suse.com>
>>>>> ---
>>>>> fs/ocfs2/acl.c | 39 +++++++++++++++++++++++++++------------
>>>>> 1 file changed, 27 insertions(+), 12 deletions(-)
>>>>>
>>>>> diff --git a/fs/ocfs2/acl.c b/fs/ocfs2/acl.c
>>>>> index bed1fcb..7e3544e 100644
>>>>> --- a/fs/ocfs2/acl.c
>>>>> +++ b/fs/ocfs2/acl.c
>>>>> @@ -283,16 +283,24 @@ int ocfs2_set_acl(handle_t *handle,
>>>>> int ocfs2_iop_set_acl(struct inode *inode, struct posix_acl *acl, int type)
>>>>> {
>>>>> struct buffer_head *bh = NULL;
>>>>> + struct ocfs2_holder *oh;
>>>>> + struct ocfs2_lock_res *lockres = &OCFS2_I(inode)->ip_inode_lockres;
>>>>> int status = 0;
>>>>> - status = ocfs2_inode_lock(inode, &bh, 1);
>>>>> - if (status < 0) {
>>>>> - if (status != -ENOENT)
>>>>> - mlog_errno(status);
>>>>> - return status;
>>>>> + oh = ocfs2_is_locked_by_me(lockres);
>>>>> + if (!oh) {
>>>>> + status = ocfs2_inode_lock(inode, &bh, 1);
>>>>> + if (status < 0) {
>>>>> + if (status != -ENOENT)
>>>>> + mlog_errno(status);
>>>>> + return status;
>>>>> + }
>>>>> }
>>>>> +
>>>>> status = ocfs2_set_acl(NULL, inode, bh, type, acl, NULL, NULL);
>>>>> - ocfs2_inode_unlock(inode, 1);
>>>>> +
>>>>> + if (!oh)
>>>>> + ocfs2_inode_unlock(inode, 1);
>>>>> brelse(bh);
>>>>> return status;
>>>>> }
>>>>> @@ -302,21 +310,28 @@ struct posix_acl *ocfs2_iop_get_acl(struct inode *inode, int type)
>>>>> struct ocfs2_super *osb;
>>>>> struct buffer_head *di_bh = NULL;
>>>>> struct posix_acl *acl;
>>>>> + struct ocfs2_holder *oh;
>>>>> + struct ocfs2_lock_res *lockres = &OCFS2_I(inode)->ip_inode_lockres;
>>>>> int ret;
>>>>> osb = OCFS2_SB(inode->i_sb);
>>>>> if (!(osb->s_mount_opt & OCFS2_MOUNT_POSIX_ACL))
>>>>> return NULL;
>>>>> - ret = ocfs2_inode_lock(inode, &di_bh, 0);
>>>>> - if (ret < 0) {
>>>>> - if (ret != -ENOENT)
>>>>> - mlog_errno(ret);
>>>>> - return ERR_PTR(ret);
>>>>> +
>>>>> + oh = ocfs2_is_locked_by_me(lockres);
>>>>> + if (!oh) {
>>>>> + ret = ocfs2_inode_lock(inode, &di_bh, 0);
>>>>> + if (ret < 0) {
>>>>> + if (ret != -ENOENT)
>>>>> + mlog_errno(ret);
>>>>> + return ERR_PTR(ret);
>>>>> + }
>>>>> }
>>>>> acl = ocfs2_get_acl_nolock(inode, type, di_bh);
>>>>> - ocfs2_inode_unlock(inode, 0);
>>>>> + if (!oh)
>>>>> + ocfs2_inode_unlock(inode, 0);
>>>>> brelse(di_bh);
>>>>> return acl;
>>>>> }
>>>>>
>>>
>>> .
>>>
>>
>
>
> .
>
next prev parent reply other threads:[~2016-11-14 5:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 5:19 [Ocfs2-devel] [RFC] Should we revert commit "ocfs2: take inode lock in ocfs2_iop_set/get_acl()"? or other ideas? Eric Ren
2016-10-19 5:19 ` [Ocfs2-devel] [DRAFT 1/2] ocfs2/dlmglue: keep track of the processes who take/put a cluster lock Eric Ren
2016-10-19 5:19 ` [Ocfs2-devel] [DRAFT 2/2] ocfs2: fix deadlock caused by recursive cluster locking Eric Ren
2016-10-31 10:55 ` piaojun
2016-11-01 1:45 ` Eric Ren
2016-11-10 10:49 ` piaojun
2016-11-11 1:56 ` Eric Ren
2016-11-14 5:42 ` piaojun [this message]
2016-11-14 10:03 ` Eric Ren
2016-11-15 2:13 ` Eric Ren
2016-11-09 4:55 ` Eric Ren
2016-10-19 6:57 ` [Ocfs2-devel] [RFC] Should we revert commit "ocfs2: take inode lock in ocfs2_iop_set/get_acl()"? or other ideas? Junxiao Bi
2016-10-19 7:46 ` Eric Ren
2016-10-24 9:13 ` Eric Ren
2016-10-28 6:20 ` Christoph Hellwig
2016-10-28 7:06 ` Eric Ren
2016-11-09 4:47 ` Eric Ren
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=58294EE2.1000900@huawei.com \
--to=piaojun@huawei.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