linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jens Osterkamp <Jens.Osterkamp@gmx.de>
To: Christoph Lameter <clameter@sgi.com>
Cc: Pekka J Enberg <penberg@cs.helsinki.fi>, linux-mm@kvack.org
Subject: Re: [BUG] in 2.6.25-rc3 with 64k page size and SLUB_DEBUG_ON
Date: Wed, 12 Mar 2008 16:19:42 +0100	[thread overview]
Message-ID: <200803121619.45708.Jens.Osterkamp@gmx.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0803071453170.9654@schroedinger.engr.sgi.com>

[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]

On Friday 07 March 2008, Christoph Lameter wrote:
> On Fri, 7 Mar 2008, Jens Osterkamp wrote:
> 
> > 0xc000000000056f08 is in copy_process (/home/auto/jens/kernels/linux-2.6.25-rc3/include/linux/slub_def.h:209).
> > 204                             struct kmem_cache *s = kmalloc_slab(size);
> > 205
> > 206                             if (!s)
> > 207                                     return ZERO_SIZE_PTR;
> > 208
> > 209                             return kmem_cache_alloc(s, flags);
> > 210                     }
> > 211             }
> > 212             return __kmalloc(size, flags);
> > 213     }
> > 
> > which is in the middle of kmalloc.
> 
> Its in the middle of inline code generated within the function that calls 
> kmalloc. Its not in kmalloc per se.
> 
> Can you figure out what the value of size is here? I suspect we are doing 
> a lookup here in kmalloc_caches with an invalid offset.

I added a printk in kmalloc and the size seems to be 0x4000.

Gruß,
	Jens

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-03-12 15:19 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-06 13:47 Jens Osterkamp
2008-03-06 19:55 ` Christoph Lameter
2008-03-06 21:07   ` Jens Osterkamp
2008-03-06 21:50     ` Christoph Lameter
2008-03-06 21:52       ` Jens Osterkamp
2008-03-06 21:56         ` Christoph Lameter
2008-03-06 22:00           ` Pekka Enberg
2008-03-06 22:04             ` Pekka Enberg
2008-03-06 22:07             ` Jens Osterkamp
2008-03-06 22:20               ` Christoph Lameter
2008-03-06 22:24                 ` Pekka Enberg
2008-03-07 12:20                   ` Jens Osterkamp
2008-03-07 12:40                     ` Pekka J Enberg
2008-03-07 12:44                       ` Pekka J Enberg
2008-03-07 22:18                         ` Jens Osterkamp
2008-03-07 22:30                       ` Jens Osterkamp
2008-03-07 22:59                         ` Christoph Lameter
2008-03-12 15:19                           ` Jens Osterkamp [this message]
2008-03-12 23:34                             ` Christoph Lameter
2008-03-18 16:44                               ` Jens Osterkamp
2008-03-18 17:45                                 ` Christoph Lameter
2008-03-18 17:51                                   ` Pekka Enberg
2008-03-06 22:25                 ` Jens Osterkamp
2008-03-07 22:09                 ` Jens Osterkamp
2008-03-06 22:21           ` Jens Osterkamp
2008-03-06 21:27 ` Pekka Enberg
2008-03-06 21:45   ` Ingo Molnar

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=200803121619.45708.Jens.Osterkamp@gmx.de \
    --to=jens.osterkamp@gmx.de \
    --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