From: Joseph Qi <jiangqi903@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>, Gang He <ghe@suse.com>
Cc: linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com
Subject: Re: [Ocfs2-devel] [PATCH] ocfs2: reflink deadlock when clone file to the same directory simultaneously
Date: Mon, 17 Oct 2022 09:51:14 +0800 [thread overview]
Message-ID: <06a7f382-5eaa-9489-3c28-aa4bfb804327@gmail.com> (raw)
In-Reply-To: <20221016162950.09db2b5f503ac87823cd1687@linux-foundation.org>
Hi Andrew,
On 10/17/22 7:29 AM, Andrew Morton via Ocfs2-devel wrote:
> On Thu, 26 Aug 2021 13:56:16 +0800 Gang He <ghe@suse.com> wrote:
>
>> So, I will send a new patch to fix this deadlock problem via dlmglue layer.
>> For this patch, I want to change the patch comments as a reflink
>> improvement patch.
>
> Did this ever happen? I've been sitting on this patch for ages.
>
Looked back this thread, the root cause of deadlock seems to be the
asynchronous of fsdlm handling. So this is not a right fix.
While for the performance improvement, I need some test data as well.
Thanks,
Joseph
next prev parent reply other threads:[~2022-10-17 1:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 11:02 [PATCH] ocfs2: reflink deadlock when clone file to the same directory simultaneously Gang He
2021-07-29 22:07 ` [Ocfs2-devel] " Wengang Wang
2021-07-30 6:16 ` Gang He
2021-07-30 16:35 ` Wengang Wang
2021-08-02 4:35 ` Gang He
2021-08-02 18:22 ` Wengang Wang
2021-08-03 1:00 ` Gang He
2021-08-04 1:57 ` Joseph Qi
2021-08-09 10:08 ` Gang He
2021-08-13 9:54 ` Joseph Qi
2021-08-18 9:20 ` Gang He
2021-08-18 11:20 ` Joseph Qi
2021-08-19 1:51 ` Gang He
2021-08-19 2:02 ` Joseph Qi
2021-08-19 6:31 ` Gang He
2021-08-26 5:56 ` [Ocfs2-devel] " Gang He
2022-10-16 23:29 ` Andrew Morton
2022-10-17 1:51 ` Joseph Qi [this message]
2022-10-17 2:29 ` Andrew Morton
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=06a7f382-5eaa-9489-3c28-aa4bfb804327@gmail.com \
--to=jiangqi903@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ghe@suse.com \
--cc=linux-kernel@vger.kernel.org \
--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).