mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Lameter <clameter@sgi.com>
To: ebiederm@xmission.com
Cc: Alexey Dobriyan <adobriyan@sw.ru>,
	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: Thu, 20 Sep 2007 10:25:46 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0709201019510.8283@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20070920075353.GA6781@localhost.sw.ru>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 2013 bytes --]

On Thu, 20 Sep 2007, Alexey Dobriyan wrote:

> OK, I do clean boot, ssh to box, then sudo slabinfo -v.
> 
> 
> =============================================================================
> BUG kmalloc-16: Object padding overwritten
> -----------------------------------------------------------------------------
> 
> INFO: 0xffff810100fd8998-0xffff810100fd8999. First byte 0xa7 instead of 0x5a
> INFO: Allocated in sysfs_new_dirent+0x100/0x120 age=11055 cpu=0 pid=3474
> INFO: Freed in kobject_uevent_env+0x123/0x430 age=11055 cpu=0 pid=3474
> INFO: Slab 0xffff810004837740 used=28 fp=0xffff810100fd89a0 flags=0x8000000000000083
> INFO: Object 0xffff810100fd8948 @offset=2376 fp=0xffff810100fd89a0

Hmmm.. A corrupted sysfs object at an offset of one word from the end of 
the object that could never have been caught by SLAB since it does not 
check more than 4 bytes. Does the value 0x5ea7 tell us anything? Maybe a 
counter was incremented a couple of times from the initial value of 0x5a5a 
that was put there by SLUB?

> INFO: 0xffff810101b45310-0xffff810101b45311. First byte 0xd3 instead of 0x5a
> INFO: Allocated in kobject_get_path+0x57/0xc0 age=18405 cpu=1 pid=2006
> INFO: Freed in kobject_uevent_env+0x123/0x430 age=18405 cpu=1 pid=2006
> INFO: Slab 0xffff81000485f718 used=8 fp=0xffff810101b45318 flags=0x8000000000000083
> INFO: Object 0xffff810101b452c0 @offset=704 fp=0xffff810101b45370
> 
> Bytes b4 0xffff810101b452b0:  db f9 fb ff 00 00 00 00 5a 5a 5a 5a 5a 5a 5a 5a Ûùûÿ....ZZZZZZZZ
>   Object 0xffff810101b452c0:  6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b a5 kkkkkkkkkkkkkkk¥
>  Redzone 0xffff810101b452d0:  bb bb bb bb bb bb bb bb                         »»»»»»»»        
>  Padding 0xffff810101b45310:  d3 5e 5a 5a 5a 5a 5a 5a                         Ó^ZZZZZZ        

Ditto.... but here we have a freed object in the above case the object is 
still in use. Done by different processes at different times.

Eric: Anything that comes to mind in sysfs?

  parent reply	other threads:[~2007-09-20 17:25 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
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 [this message]
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.0709201019510.8283@schroedinger.engr.sgi.com \
    --to=clameter@sgi.com \
    --cc=adobriyan@sw.ru \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --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®