linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <clameter@sgi.com>
To: Yoichi Yuasa <yoichi_yuasa@tripeaks.co.jp>
Cc: linux-mm@kvack.org, Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: Collision of SLUB unique ID
Date: Tue, 10 Jun 2008 10:06:20 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0806101005140.16992@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <200806100244.m5A2iZbV021848@po-mbox301.hop.2iij.net>

On Tue, 10 Jun 2008, Yoichi Yuasa wrote:

> No, the kernel that applies it cannot boot. 

Hmmm... Ok here is an experimental patch that just disables merging for 
192 (in general a bad idea). If this works then we know at least where
to look for the solution.

---
 mm/slub.c |    5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

Index: linux-2.6/mm/slub.c
===================================================================
--- linux-2.6.orig/mm/slub.c	2008-06-10 10:02:03.000000000 -0700
+++ linux-2.6/mm/slub.c	2008-06-10 10:04:04.000000000 -0700
@@ -171,7 +171,7 @@ static inline void ClearSlabDebug(struct
  * Set of flags that will prevent slab merging
  */
 #define SLUB_NEVER_MERGE (SLAB_RED_ZONE | SLAB_POISON | SLAB_STORE_USER | \
-		SLAB_TRACE | SLAB_DESTROY_BY_RCU)
+		SLAB_TRACE | SLAB_DESTROY_BY_RCU | __SLAB_NOMERGE)
 
 #define SLUB_MERGE_SAME (SLAB_DEBUG_FREE | SLAB_RECLAIM_ACCOUNT | \
 		SLAB_CACHE_DMA)
@@ -187,6 +187,7 @@ static inline void ClearSlabDebug(struct
 /* Internal SLUB flags */
 #define __OBJECT_POISON		0x80000000 /* Poison object */
 #define __SYSFS_ADD_DEFERRED	0x40000000 /* Not yet visible via sysfs */
+#define __SLAB_NOMERGE		0x20000000 /* Never merge this slab */
 
 static int kmem_size = sizeof(struct kmem_cache);
 
@@ -2998,7 +2999,7 @@ void __init kmem_cache_init(void)
 	}
 	if (KMALLOC_MIN_SIZE <= 128) {
 		create_kmalloc_cache(&kmalloc_caches[2],
-				"kmalloc-192", 192, GFP_KERNEL);
+				"kmalloc-192", 192, GFP_KERNEL | __SLAB_NOMERGE);
 		caches++;
 	}
 

--
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:[~2008-06-10 17: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
2008-06-10  1:22     ` Christoph Lameter
2008-06-10  2:44       ` Yoichi Yuasa
2008-06-10 17:06         ` Christoph Lameter [this message]

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=Pine.LNX.4.64.0806101005140.16992@schroedinger.engr.sgi.com \
    --to=clameter@sgi.com \
    --cc=linux-mm@kvack.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=yoichi_yuasa@tripeaks.co.jp \
    /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