From: Yoichi Yuasa <yoichi_yuasa@tripeaks.co.jp>
To: Christoph Lameter <clameter@sgi.com>
Cc: yoichi_yuasa@tripeaks.co.jp, linux-mm@kvack.org,
Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: Collision of SLUB unique ID
Date: Tue, 10 Jun 2008 10:06:45 +0900 [thread overview]
Message-ID: <200806100106.m5A16iKl025150@po-mbox304.hop.2iij.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0806090706230.29723@schroedinger.engr.sgi.com>
On Mon, 9 Jun 2008 07:10:56 -0700 (PDT)
Christoph Lameter <clameter@sgi.com> wrote:
> On Wed, 4 Jun 2008, Yoichi Yuasa wrote:
>
> > I'm testing SLUB on Cobalt(MIPS machine).
> > I got the following error messages at the boot time.
> >
> > The Cobalt's ARCH_KMALLOC_MINALIGN is 128.
> > At this time, kmalloc-192 unique ID has collided with kmalloc-256.
>
> Hmmm... The system should alias the 192 byte cache to the 256 sized one.
>
> What kernel version is this? We could have broken this in 2.6.25 with the
> addtional flags that were added. But then it should be okay again for
> 2.6.26-rcX which removed those additional flags. If this is indeed the
> case then we need a fix for stable and mainline is fine.
2.6.24, 2.6.25.5 and 2.6.26-rc5.
I got same error on these version.
Yoichi
--
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>
next prev parent reply other threads:[~2008-06-10 1:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-04 14:46 Yoichi Yuasa
2008-06-09 14:10 ` Christoph Lameter
2008-06-10 1:06 ` Yoichi Yuasa [this message]
2008-06-10 1:22 ` Christoph Lameter
2008-06-10 2:44 ` Yoichi Yuasa
2008-06-10 17:06 ` Christoph Lameter
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=200806100106.m5A16iKl025150@po-mbox304.hop.2iij.net \
--to=yoichi_yuasa@tripeaks.co.jp \
--cc=clameter@sgi.com \
--cc=linux-mm@kvack.org \
--cc=penberg@cs.helsinki.fi \
/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