From: Sunil Mushran <sunil.mushran@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] Wakeup down-convert thread just after clearing OCFS2_LOCK_UPCONVERT_FINISHING -v3
Date: Thu, 15 Sep 2011 17:53:39 -0700 [thread overview]
Message-ID: <4E729E13.5070800@oracle.com> (raw)
In-Reply-To: <20110916004200.GA3433@laptop.jp.oracle.com>
On 09/15/2011 05:42 PM, Wengang Wang wrote:
> Hi Sunil,
>
> On 11-09-15 10:21, Sunil Mushran wrote:
>> http://people.redhat.com/~teigland/make_panic
>>
>> This test has been useful in exposing dlmglue issues.
>>
>> On 09/15/2011 10:15 AM, Sunil Mushran wrote:
>>> I am fine with the kick in recover from dlm error. Not so in cluster lock.
>>> We have to be very very sure before meddling with that function. It is
>>> a state machine with many hidden gotchas.
>>>
>>> So is this patch for a bug encountered or just code audit. Also, what kind
>>> testing has been done.
> Yes, a bug(hang) encountered. After testing and analysis, I found the root cause.
> And it's NOT the dlm error case. The hang was fixed by the original patch.
> I will email you about the orabug and testcase(pretty easy to reproduce).
Which original patch?
> I will try http://people.redhat.com/~teigland/make_panic to see if it
> can find something.
next prev parent reply other threads:[~2011-09-16 0:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 3:27 [Ocfs2-devel] [PATCH] Wakeup down-convert thread just after clearing OCFS2_LOCK_UPCONVERT_FINISHING -v3 Wengang Wang
2011-09-15 17:15 ` Sunil Mushran
2011-09-15 17:21 ` Sunil Mushran
2011-09-16 0:42 ` Wengang Wang
2011-09-16 0:53 ` Sunil Mushran [this message]
2011-09-16 0:57 ` Wengang Wang
2011-11-17 9:33 ` Joel Becker
-- strict thread matches above, loose matches on Subject: below --
2011-09-23 0:49 Wengang Wang
2011-09-23 0:53 ` Sunil Mushran
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=4E729E13.5070800@oracle.com \
--to=sunil.mushran@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 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.