All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Stefan Lippers-Hollmann <s.L-H@gmx.de>,
	linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	cl@linux-foundation.org, dave@linux.vnet.ibm.com,
	ebmunson@us.ibm.com, mel@csn.ul.ie, stable@kernel.org
Subject: Re: patch mm-fix-committed_as-underflow-on-large-nr_cpus-environment.patch added to 2.6.29-stable tree
Date: Tue, 5 May 2009 23:20:58 -0700	[thread overview]
Message-ID: <20090506062058.GA6916@suse.de> (raw)
In-Reply-To: <2f11576a0905051612p140e077fva214e954273a39df@mail.gmail.com>

On Wed, May 06, 2009 at 08:12:21AM +0900, KOSAKI Motohiro wrote:
> > On Wed, May 06, 2009 at 07:26:51AM +0900, KOSAKI Motohiro wrote:
> >> Could you please post oops log?
> >> current mmotm (include this patch) works fine on my x86_64 box. Then,
> >> I have no hint now ;-)
> >
> > Attached is a picture of the oops.
> >
> > Hope this helps,
> 
> OK, the reason is 99% mis-applied patch. I've made rebased patch.
> 
> in my environment
> 
> 2.6.29.2 + original patch:  panic
> 2.6.29.2 + rebased patch:  works well
> 
> Could you please try it?

thank you for looking into this, I'll try it out tomorrow morning and
let you know how it goes.

greg k-h

  reply	other threads:[~2009-05-06  6:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090504220454.3F71148FB8@coco.kroah.org>
     [not found] ` <200905052036.24106.s.L-H@gmx.de>
2009-05-05 20:53   ` patch mm-fix-committed_as-underflow-on-large-nr_cpus-environment.patch added to 2.6.29-stable tree Greg KH
2009-05-05 22:14   ` Greg KH
2009-05-05 22:26     ` KOSAKI Motohiro
2009-05-05 22:40       ` Greg KH
2009-05-05 22:58         ` KOSAKI Motohiro
2009-05-05 22:59       ` Greg KH
2009-05-05 23:12         ` KOSAKI Motohiro
2009-05-06  6:20           ` Greg KH [this message]
2009-05-06 16:37             ` [stable] " Greg KH
2009-05-06 16:46           ` Stefan Lippers-Hollmann

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=20090506062058.GA6916@suse.de \
    --to=gregkh@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux-foundation.org \
    --cc=dave@linux.vnet.ibm.com \
    --cc=ebmunson@us.ibm.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mel@csn.ul.ie \
    --cc=s.L-H@gmx.de \
    --cc=stable@kernel.org \
    /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.