All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junxiao Bi <junxiao.bi@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: dlm: fix lock migration crash
Date: Thu, 27 Feb 2014 09:24:31 +0800	[thread overview]
Message-ID: <530E93CF.8020608@oracle.com> (raw)
In-Reply-To: <20140226164856.a127c84a1df19a82dc24f21c@linux-foundation.org>

Hi Andrew,

On 02/27/2014 08:48 AM, Andrew Morton wrote:
> On Wed, 26 Feb 2014 15:47:37 +0800 Junxiao Bi <junxiao.bi@oracle.com> wrote:
>
>> This issue was introduced by commit 800deef3 where it replaced list_for_each
>> with list_for_each_entry. The variable "lock" will point to invalid data if
>> "tmpq" list is empty and a panic will be triggered due to this.
>> Sunil advised reverting it back, but the old version was also not right. At
>> the end of the outer for loop, that list_for_each_entry will also set "lock"
>> to an invalid data, then in the next loop, if the "tmpq" list is empty, "lock"
>> will be an stale invalid data and cause the panic. So reverting the list_for_each
>> back and reset "lock" to NULL to fix this issue.
>>
>> ...
>>
>> Cc: <stable@vger.kernel.org>
> 800deef3 was back in 2007, so this doesn't seem a terribly urgent bugfix!
>
> I think what I'll do is to target 3.15-rc1 to give people time to
> review and test this.  But I'll retain the cc:stable so the fix gets
> backported into 3.14.x and earlier kernels.
>
> OK?
OK.  Thanks for merging it.

Thanks,
Junxiao.

  reply	other threads:[~2014-02-27  1:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-26  7:47 [Ocfs2-devel] [PATCH] ocfs2: dlm: fix lock migration crash Junxiao Bi
2014-02-26  7:51 ` Wengang
2014-02-27  0:48 ` Andrew Morton
2014-02-27  1:24   ` Junxiao Bi [this message]
2014-02-27  2:10 ` Srinivas Eeda

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=530E93CF.8020608@oracle.com \
    --to=junxiao.bi@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.