mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Lameter <clameter@sgi.com>
To: Alexey Dobriyan <adobriyan@sw.ru>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	gregkh@suse.de, linux-kernel@vger.kernel.org
Subject: Re: 2.6.23-rc6-mm1: BUG kmalloc-16: Object padding overwritten (sysfs?)
Date: Wed, 19 Sep 2007 14:36:04 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0709191432200.3111@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0709191355340.3136@schroedinger.engr.sgi.com>

On Wed, 19 Sep 2007, Christoph Lameter wrote:

> Hmmm... This works fine here. Doing the cat may trigger slab validation 
> and show objects corruptions that were heretofore unnoticed.

Not exactly true since reading a file cannot trigger slab validation. The 
catting of all files will touch the following:

clameter@schroedinger:/sys/slab/kmalloc-64$ ls -l
total 0
-r--r--r-- 1 root root 4096 Sep 19 14:28 aliases
-r--r--r-- 1 root root 4096 Sep 19 14:28 align
-r--r--r-- 1 root root 4096 Sep 19 14:28 alloc_calls
-r--r--r-- 1 root root 4096 Sep 19 14:28 cache_dma
-r--r--r-- 1 root root 4096 Sep 19 14:28 cpu_slabs
-r--r--r-- 1 root root 4096 Sep 19 14:28 ctor
-r--r--r-- 1 root root 4096 Sep 19 14:28 destroy_by_rcu
-r--r--r-- 1 root root 4096 Sep 19 14:28 free_calls
-r--r--r-- 1 root root 4096 Sep 19 14:28 hwcache_align
-r--r--r-- 1 root root 4096 Sep 19 14:28 object_size
-r--r--r-- 1 root root 4096 Sep 19 14:28 objects
-r--r--r-- 1 root root 4096 Sep 19 14:28 objs_per_slab
-r--r--r-- 1 root root 4096 Sep 19 14:28 order
-r--r--r-- 1 root root 4096 Sep 19 14:28 partial
-rw-r--r-- 1 root root 4096 Sep 19 14:28 poison
-rw-r--r-- 1 root root 4096 Sep 19 14:28 reclaim_account
-rw-r--r-- 1 root root 4096 Sep 19 14:28 red_zone
-rw-r--r-- 1 root root 4096 Sep 19 14:28 sanity_checks
-rw-r--r-- 1 root root 4096 Sep 19 14:28 shrink
-r--r--r-- 1 root root 4096 Sep 19 14:28 slab_size
-r--r--r-- 1 root root 4096 Sep 19 14:28 slabs
-rw-r--r-- 1 root root 4096 Sep 19 14:28 store_user
-rw-r--r-- 1 root root 4096 Sep 19 14:28 trace
-rw-r--r-- 1 root root    0 Sep 19 14:28 validate

catting

	alloc_calls

and
	free_calls

will perform a global scan over all objects to determine the callers. 
Before we do that we have to flush the per cpu slabs. The trace shows that 
one of the errors was detected in there and the other one probably later.

So I would think that this is an actual memory corruption issue on your 
system and the /sys/slab stuff works fine. slabinfo -v will perform a more 
details scan to help you located the problem.


  reply	other threads:[~2007-09-19 21:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-19 12:39 Alexey Dobriyan
2007-09-19 12:59 ` Alexey Dobriyan
2007-09-19 19:39   ` Andrew Morton
2007-09-19 20:59     ` Christoph Lameter
2007-09-19 21:36       ` Christoph Lameter [this message]
2007-09-20  7:53         ` Alexey Dobriyan
2007-09-20 10:32           ` Alexey Dobriyan
2007-09-20 17:36             ` Christoph Lameter
2007-09-21  7:16               ` Alexey Dobriyan
2007-09-20 17:25           ` Christoph Lameter
2007-09-20 17:37             ` Christoph Lameter
2007-09-20 18:54               ` Eric W. Biederman

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.0709191432200.3111@schroedinger.engr.sgi.com \
    --to=clameter@sgi.com \
    --cc=adobriyan@sw.ru \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®