All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sachin Sant <sachinp@in.ibm.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Linux/PPC Development <linuxppc-dev@ozlabs.org>,
	linux-mm@kvack.org, linux-kernel <linux-kernel@vger.kernel.org>,
	maciej.rutecki@gmail.com
Subject: Re: 2.6.35-rc2 : OOPS with LTP memcg regression test run.
Date: Fri, 11 Jun 2010 11:09:20 +0530	[thread overview]
Message-ID: <4C11CC08.9080503@in.ibm.com> (raw)
In-Reply-To: <20100611103509.520671b2.kamezawa.hiroyu@jp.fujitsu.com>

KAMEZAWA Hiroyuki wrote:
> On Thu, 10 Jun 2010 22:00:57 +0200
> Maciej Rutecki <maciej.rutecki@gmail.com> wrote:
>
>   
>> I created a Bugzilla entry at 
>> https://bugzilla.kernel.org/show_bug.cgi?id=16178
>> for your bug report, please add your address to the CC list in there, thanks!
>>
>>     
>
> Hmm... It seems a panic in SLUB or SLAB.
> Is .config available ?
>   
I think the root cause for this problem was same as the one
mentioned in this thread (Bug kmalloc-4096 : Poison overwritten)

http://marc.info/?l=linux-kernel&m=127586004308747&w=2 <http://marc.info/?l=linux-kernel&m=127586004308747&w=2>

I verified that the problem goes away after applying the commit 386f40c.

Thanks
-Sachin 


-- 

---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------

WARNING: multiple messages have this Message-ID (diff)
From: Sachin Sant <sachinp@in.ibm.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: maciej.rutecki@gmail.com,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-mm@kvack.org,
	Linux/PPC Development <linuxppc-dev@ozlabs.org>
Subject: Re: 2.6.35-rc2 : OOPS with LTP memcg regression test run.
Date: Fri, 11 Jun 2010 11:09:20 +0530	[thread overview]
Message-ID: <4C11CC08.9080503@in.ibm.com> (raw)
In-Reply-To: <20100611103509.520671b2.kamezawa.hiroyu@jp.fujitsu.com>

KAMEZAWA Hiroyuki wrote:
> On Thu, 10 Jun 2010 22:00:57 +0200
> Maciej Rutecki <maciej.rutecki@gmail.com> wrote:
>
>   
>> I created a Bugzilla entry at 
>> https://bugzilla.kernel.org/show_bug.cgi?id=16178
>> for your bug report, please add your address to the CC list in there, thanks!
>>
>>     
>
> Hmm... It seems a panic in SLUB or SLAB.
> Is .config available ?
>   
I think the root cause for this problem was same as the one
mentioned in this thread (Bug kmalloc-4096 : Poison overwritten)

http://marc.info/?l=linux-kernel&m=127586004308747&w=2 <http://marc.info/?l=linux-kernel&m=127586004308747&w=2>

I verified that the problem goes away after applying the commit 386f40c.

Thanks
-Sachin 


-- 

---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------


WARNING: multiple messages have this Message-ID (diff)
From: Sachin Sant <sachinp@in.ibm.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: maciej.rutecki@gmail.com,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-mm@kvack.org,
	Linux/PPC Development <linuxppc-dev@ozlabs.org>
Subject: Re: 2.6.35-rc2 : OOPS with LTP memcg regression test run.
Date: Fri, 11 Jun 2010 11:09:20 +0530	[thread overview]
Message-ID: <4C11CC08.9080503@in.ibm.com> (raw)
In-Reply-To: <20100611103509.520671b2.kamezawa.hiroyu@jp.fujitsu.com>

KAMEZAWA Hiroyuki wrote:
> On Thu, 10 Jun 2010 22:00:57 +0200
> Maciej Rutecki <maciej.rutecki@gmail.com> wrote:
>
>   
>> I created a Bugzilla entry at 
>> https://bugzilla.kernel.org/show_bug.cgi?id=16178
>> for your bug report, please add your address to the CC list in there, thanks!
>>
>>     
>
> Hmm... It seems a panic in SLUB or SLAB.
> Is .config available ?
>   
I think the root cause for this problem was same as the one
mentioned in this thread (Bug kmalloc-4096 : Poison overwritten)

http://marc.info/?l=linux-kernel&m=127586004308747&w=2 <http://marc.info/?l=linux-kernel&m=127586004308747&w=2>

I verified that the problem goes away after applying the commit 386f40c.

Thanks
-Sachin 


-- 

---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2010-06-11  5:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-06 15:06 2.6.35-rc2 : OOPS with LTP memcg regression test run Sachin Sant
2010-06-06 15:06 ` Sachin Sant
2010-06-06 15:40 ` Al Viro
2010-06-06 15:40   ` Al Viro
2010-06-06 15:40   ` Al Viro
2010-06-06 16:15   ` Markus Trippelsdorf
2010-06-06 16:15     ` Markus Trippelsdorf
2010-06-06 16:15     ` Markus Trippelsdorf
2010-06-10 20:00 ` Maciej Rutecki
2010-06-10 20:00   ` Maciej Rutecki
2010-06-10 20:00   ` Maciej Rutecki
2010-06-11  1:35   ` KAMEZAWA Hiroyuki
2010-06-11  1:35     ` KAMEZAWA Hiroyuki
2010-06-11  1:35     ` KAMEZAWA Hiroyuki
2010-06-11  5:39     ` Sachin Sant [this message]
2010-06-11  5:39       ` Sachin Sant
2010-06-11  5:39       ` Sachin Sant

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=4C11CC08.9080503@in.ibm.com \
    --to=sachinp@in.ibm.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=maciej.rutecki@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 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.