From: piaojun <piaojun@huawei.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] ocfs2/dlm: continue to purge recovery lockres when recovery master goes down
Date: Tue, 12 Jul 2016 10:20:40 +0800 [thread overview]
Message-ID: <578453F8.1040407@huawei.com> (raw)
In-Reply-To: <20160711133738.06b386f800bdfcdcc10e6d52@linux-foundation.org>
On 2016-7-12 4:37, Andrew Morton wrote:
> On Mon, 11 Jul 2016 13:34:30 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
>
>> On Sun, 10 Jul 2016 18:04:33 +0800 piaojun <piaojun@huawei.com> wrote:
>>
>>> We found a dlm-blocked situation caused by continuous breakdown of
>>> recovery masters described below. To solve this problem, we should purge
>>> recovery lock once detecting recovery master goes down.
>>
>> I'm not sure which kernel version this patch is against, but I get
>> significant rejects when merging into 4.7-rc7. Can you please redo it
>> against the latest Linus tree?
>
> Oh, OK, it's probably due to changes in your earlier patches. It helps
> if you use sequence numbering:
>
> [patch 1/3] ocfs2/dlm: disable BUG_ON when DLM_LOCK_RES_DROPPING_REF, is cleared before dlm_deref_lockres_done_handler
> [patch 2/3] ocfs2/dlm: solve a BUG when deref failed in dlm_drop_lockres_ref
> etc
>
> .
>
Thanks for remainder, I have sent [PATCH v2] to fix it.
prev parent reply other threads:[~2016-07-12 2:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-10 10:04 [Ocfs2-devel] ocfs2/dlm: continue to purge recovery lockres when recovery master goes down piaojun
2016-07-11 2:09 ` Joseph Qi
2016-07-11 20:34 ` Andrew Morton
2016-07-11 20:37 ` Andrew Morton
2016-07-12 2:20 ` piaojun [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=578453F8.1040407@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.