All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Joseph Qi <jiangqi903@gmail.com>
Cc: Eric Ren <zren@suse.com>,
	ocfs2-devel@oss.oracle.com, mfasheh@versity.com,
	jlbec@evilplan.org, teigland@redhat.com, ghe@suse.com,
	junxiao.bi@oracle.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ocfs2: fix crash caused by stale lvb with fsdlm plugin
Date: Tue, 20 Dec 2016 14:51:26 -0800	[thread overview]
Message-ID: <20161220145126.5ee33b840f9967aae2e63806@linux-foundation.org> (raw)
In-Reply-To: <6ddf36d1-9e2b-f094-77a4-6ec6d6661dc2@gmail.com>

On Mon, 19 Dec 2016 17:55:06 +0800 Joseph Qi <jiangqi903@gmail.com> wrote:

> > I'd like to see this quick and small fix to be merged at this moment, 
> > because this issue is little emergency for us.
> > Anyway, we can supersede this one easily if someone familiar with o2cb 
> > works out a patch for o2cb in the future.
> >
> > Does this sounds good to you?
> 
> Fine.
> Reviewed-by: Joseph Qi <jiangqi903@gmail.com>

I'll add cc:stable to this one so the fix gets backported into older
kernels.

WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Joseph Qi <jiangqi903@gmail.com>
Cc: Eric Ren <zren@suse.com>,
	ocfs2-devel@oss.oracle.com, mfasheh@versity.com,
	jlbec@evilplan.org, teigland@redhat.com, ghe@suse.com,
	junxiao.bi@oracle.com, linux-kernel@vger.kernel.org
Subject: [Ocfs2-devel] [PATCH] ocfs2: fix crash caused by stale lvb with fsdlm plugin
Date: Tue, 20 Dec 2016 14:51:26 -0800	[thread overview]
Message-ID: <20161220145126.5ee33b840f9967aae2e63806@linux-foundation.org> (raw)
In-Reply-To: <6ddf36d1-9e2b-f094-77a4-6ec6d6661dc2@gmail.com>

On Mon, 19 Dec 2016 17:55:06 +0800 Joseph Qi <jiangqi903@gmail.com> wrote:

> > I'd like to see this quick and small fix to be merged at this moment, 
> > because this issue is little emergency for us.
> > Anyway, we can supersede this one easily if someone familiar with o2cb 
> > works out a patch for o2cb in the future.
> >
> > Does this sounds good to you?
> 
> Fine.
> Reviewed-by: Joseph Qi <jiangqi903@gmail.com>

I'll add cc:stable to this one so the fix gets backported into older
kernels.

  reply	other threads:[~2016-12-20 22:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-09  9:30 [PATCH] ocfs2: fix crash caused by stale lvb with fsdlm plugin Eric Ren
2016-12-09  9:30 ` [Ocfs2-devel] " Eric Ren
2016-12-12  2:56 ` Gang He
2016-12-12  2:56   ` [Ocfs2-devel] " Gang He
2016-12-12  3:23   ` Eric Ren
2016-12-12  3:23     ` Eric Ren
2016-12-15  1:46 ` Joseph Qi
2016-12-15  1:46   ` [Ocfs2-devel] " Joseph Qi
2016-12-15  2:27   ` Eric Ren
2016-12-15  2:27     ` [Ocfs2-devel] " Eric Ren
2016-12-19  9:55     ` Joseph Qi
2016-12-19  9:55       ` [Ocfs2-devel] " Joseph Qi
2016-12-20 22:51       ` Andrew Morton [this message]
2016-12-20 22:51         ` Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2016-12-09  9:24 Eric Ren
2016-12-09  9:45 ` Eric Ren

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=20161220145126.5ee33b840f9967aae2e63806@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=ghe@suse.com \
    --cc=jiangqi903@gmail.com \
    --cc=jlbec@evilplan.org \
    --cc=junxiao.bi@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfasheh@versity.com \
    --cc=ocfs2-devel@oss.oracle.com \
    --cc=teigland@redhat.com \
    --cc=zren@suse.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.