linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Srinivas Eeda <srinivas.eeda@oracle.com>
To: richard -rw- weinberger <richard.weinberger@gmail.com>
Cc: "Ramappa, Ravi (NSN - IN/Bangalore)" <ravi.ramappa@nsn.com>,
	"ocfs2-users@oss.oracle.com" <ocfs2-users@oss.oracle.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	david@sigma-star.at
Subject: Re: [Ocfs2-users] Kernel panic due to ocfs2
Date: Wed, 27 Feb 2013 20:54:13 -0800	[thread overview]
Message-ID: <512EE2F5.2080900@oracle.com> (raw)
In-Reply-To: <CAFLxGvycGCyeg7AhJ=3J0ztZfgYLmyKZSrzNUd5ymAb-tSd4qg@mail.gmail.com>

On 02/27/2013 03:52 AM, richard -rw- weinberger wrote:
> On Tue, Feb 26, 2013 at 8:54 AM, richard -rw- weinberger
> <richard.weinberger@gmail.com> wrote:
>> On Tue, Feb 26, 2013 at 7:31 AM, Srinivas Eeda <srinivas.eeda@oracle.com> wrote:
>>> This is due to a race in lock mastery/purge. I have recently fixed this
>>> problem but haven't yet submitted the patch to mainline. Please file a
>>> Service request with Oracle to get a one-off fix.
>> Please submit the patch immediately.
>> Why does one need a f§&"!#$ SR from Oracle to have this fixed?
> So, where can I find this patch?
> Can you please share it with us insignificant and rubbishy community folks?
Here is the patch against mainline which I haven't yet submitted because 
I have not finished testing on mainline kernel yet. I am running into 
another unrelated crashes during testing. I am forwarding the patch to 
you assuming you are looking for this fix.

https://oss.oracle.com/~seeda/patches/dlm-race/

The other person who emailed about the problem was running older ocfs2 
version(1.4-10). Which is where I originally debugged, patched and 
tested the fix. So I offered to help him.
>
> https://oss.oracle.com/projects/ocfs2/source.html points to
> http://git.kernel.org/?p=linux/kernel/git/jlbec/ocfs2.git;a=summary
> This tree seems horrible outdated...
>

  parent reply	other threads:[~2013-02-28  4:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <EB937501617BFC44BE90EDA24CA6A13A0117EB@SGSIMBX003.nsn-intra.net>
     [not found] ` <512C56AF.1030801@oracle.com>
2013-02-26  7:54   ` [Ocfs2-users] Kernel panic due to ocfs2 richard -rw- weinberger
2013-02-27 11:52     ` richard -rw- weinberger
2013-02-27 11:57       ` Sedat Dilek
2013-02-27 12:06         ` richard -rw- weinberger
2013-02-28  4:54       ` Srinivas Eeda [this message]
2013-02-28  7:05         ` richard -rw- weinberger

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=512EE2F5.2080900@oracle.com \
    --to=srinivas.eeda@oracle.com \
    --cc=david@sigma-star.at \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ocfs2-users@oss.oracle.com \
    --cc=ravi.ramappa@nsn.com \
    --cc=richard.weinberger@gmail.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).