From: Junxiao Bi <junxiao.bi@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: check if the ocfs2 lock resource be initialized before calling ocfs2_dlm_lock
Date: Thu, 16 Apr 2015 15:28:07 +0800 [thread overview]
Message-ID: <552F6487.4020707@oracle.com> (raw)
In-Reply-To: <5518C165.10106@huawei.com>
Hi Alex,
On 03/30/2015 11:22 AM, alex chen wrote:
> If ocfs2 lockres has not been initialized before calling ocfs2_dlm_lock,
> the lock won't be dropped and then will lead umount hung. The case is
> described below:
>
> ocfs2_mknod
> ocfs2_mknod_locked
> __ocfs2_mknod_locked
> ocfs2_journal_access_di
> Failed because of -ENOMEM or other reasons, the inode lockres
> has not been initialized yet.
If failed here, is OCFS2_I(inode)->ip_inode_lockres initialized? If not
how can you break __ocfs2_cluster_lock with the following condition?
if (!(lockres->l_flags & OCFS2_LOCK_INITIALIZED))
Thanks,
Junxiao.
>
> iput(inode)
> ocfs2_evict_inode
> ocfs2_delete_inode
> ocfs2_inode_lock
> ocfs2_inode_lock_full_nested
> __ocfs2_cluster_lock
> Succeeds and allocates a new dlm lockres.
> ocfs2_clear_inode
> ocfs2_open_unlock
> ocfs2_drop_inode_locks
> ocfs2_drop_lock
> Since lockres has not been initialized, the lock
> can't be dropped and the lockres can't be
> migrated, thus umount will hang forever.
>
> Signed-off-by: Alex Chen <alex.chen@huawei.com>
> Reviewed-by: Joseph Qi <joseph.qi@huawei.com>
> Reviewed-by: joyce.xue <xuejiufei@huawei.com>
>
> ---
> fs/ocfs2/dlmglue.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/fs/ocfs2/dlmglue.c b/fs/ocfs2/dlmglue.c
> index 11849a4..8b23aa2 100644
> --- a/fs/ocfs2/dlmglue.c
> +++ b/fs/ocfs2/dlmglue.c
> @@ -1391,6 +1391,11 @@ static int __ocfs2_cluster_lock(struct ocfs2_super *osb,
> int noqueue_attempted = 0;
> int dlm_locked = 0;
>
> + if (!(lockres->l_flags & OCFS2_LOCK_INITIALIZED)) {
> + mlog_errno(-EINVAL);
> + return -EINVAL;
> + }
> +
> ocfs2_init_mask_waiter(&mw);
>
> if (lockres->l_ops->flags & LOCK_TYPE_USES_LVB)
>
next prev parent reply other threads:[~2015-04-16 7:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 3:22 [Ocfs2-devel] [PATCH] ocfs2: check if the ocfs2 lock resource be initialized before calling ocfs2_dlm_lock alex chen
2015-03-31 22:13 ` Andrew Morton
2015-04-01 0:43 ` Joseph Qi
2015-04-01 2:19 ` Andrew Morton
2015-04-02 3:14 ` alex chen
2015-04-02 3:45 ` Andrew Morton
2015-04-16 7:28 ` Junxiao Bi [this message]
2015-04-21 2:54 ` alex chen
2015-04-22 1:46 ` Junxiao Bi
2015-04-22 8:14 ` alex chen
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=552F6487.4020707@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