From: WeiWei Wang <wangww631@huawei.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: fix race between dio and recover orphan
Date: Fri, 26 Jun 2015 15:17:13 +0800 [thread overview]
Message-ID: <558CFC79.5050808@huawei.com> (raw)
In-Reply-To: <558CE8B4.8070904@huawei.com>
On 2015/6/26 13:52, Joseph Qi wrote:
> During direct io the inode will be added to orphan first and then
> deleted from orphan. There is a race window that the orphan entry will
> be deleted twice and thus trigger the BUG when validating
> OCFS2_DIO_ORPHANED_FL in ocfs2_del_inode_from_orphan.
>
> ocfs2_direct_IO_write
> ...
> ocfs2_add_inode_to_orphan
> >>>>>>>> race window, another node may rm the file and then down,
> this node take care of orphan recovery and clear flag
> OCFS2_DIO_ORPHANED_FL
> ocfs2_del_inode_from_orphan
>
> Take inode mutex lock to fix this race case.
>
> Reported-by: Yiwen Jiang <jiangyiwen@huawei.com>
> Signed-off-by: Joseph Qi <joseph.qi@huawei.com>
Reviewed-by: Weiwei Wang <wangww631@huawei.com>
> ---
> fs/ocfs2/journal.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/fs/ocfs2/journal.c b/fs/ocfs2/journal.c
> index 8017032..f8206d1 100644
> --- a/fs/ocfs2/journal.c
> +++ b/fs/ocfs2/journal.c
> @@ -2172,6 +2172,7 @@ static int ocfs2_recover_orphans(struct ocfs2_super *osb,
> iter = oi->ip_next_orphan;
> oi->ip_next_orphan = NULL;
>
> + mutex_lock(&inode->i_mutex);
> ret = ocfs2_rw_lock(inode, 1);
> if (ret < 0) {
> mlog_errno(ret);
> @@ -2218,6 +2219,7 @@ unlock_inode:
> unlock_rw:
> ocfs2_rw_unlock(inode, 1);
> next:
> + mutex_unlock(&inode->i_mutex);
> iput(inode);
> brelse(di_bh);
> di_bh = NULL;
>
prev parent reply other threads:[~2015-06-26 7:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 5:52 [Ocfs2-devel] [PATCH] ocfs2: fix race between dio and recover orphan Joseph Qi
2015-06-26 7:17 ` WeiWei Wang [this message]
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=558CFC79.5050808@huawei.com \
--to=wangww631@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