From: Alexey Dobriyan <adobriyan@sw.ru>
To: Christoph Lameter <clameter@sgi.com>
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: Thu, 20 Sep 2007 11:53:54 +0400 [thread overview]
Message-ID: <20070920075353.GA6781@localhost.sw.ru> (raw)
In-Reply-To: <Pine.LNX.4.64.0709191432200.3111@schroedinger.engr.sgi.com>
On Wed, Sep 19, 2007 at 02:36:04PM -0700, Christoph Lameter wrote:
> 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.
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
Bytes b4 0xffff810100fd8938: f1 f9 fb ff 00 00 00 00 5a 5a 5a 5a 5a 5a 5a 5a ñùûÿ....ZZZZZZZZ
Object 0xffff810100fd8948: 73 75 62 73 79 73 74 65 6d 00 6b 6b 6b 6b 6b a5 subsystem.kkkkk¥
Redzone 0xffff810100fd8958: cc cc cc cc cc cc cc cc ÌÌÌÌÌÌÌÌ
Padding 0xffff810100fd8998: a7 5e 5a 5a 5a 5a 5a 5a §^ZZZZZZ
Call Trace:
[<ffffffff802827c8>] check_bytes_and_report+0xb8/0x100
[<ffffffff80282c34>] check_object+0x234/0x270
[<ffffffff80282e51>] validate_slab_slab+0x1e1/0x280
[<ffffffff8028591e>] validate_store+0xde/0x1c0
[<ffffffff802819e7>] slab_attr_store+0x27/0x30
[<ffffffff802cc9da>] sysfs_write_file+0xca/0x140
[<ffffffff80288d2d>] vfs_write+0xad/0xe0
[<ffffffff80289313>] sys_write+0x53/0x90
[<ffffffff8020bcae>] system_call+0x7e/0x83
FIX kmalloc-16: Restoring 0xffff810100fd8998-0xffff810100fd8999=0x5a
=============================================================================
BUG kmalloc-16: Object padding overwritten
-----------------------------------------------------------------------------
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
Call Trace:
[<ffffffff802827c8>] check_bytes_and_report+0xb8/0x100
[<ffffffff80282c34>] check_object+0x234/0x270
[<ffffffff80282dcf>] validate_slab_slab+0x15f/0x280
[<ffffffff8028591e>] validate_store+0xde/0x1c0
[<ffffffff802819e7>] slab_attr_store+0x27/0x30
[<ffffffff802cc9da>] sysfs_write_file+0xca/0x140
[<ffffffff80288d2d>] vfs_write+0xad/0xe0
[<ffffffff80289313>] sys_write+0x53/0x90
[<ffffffff8020bcae>] system_call+0x7e/0x83
FIX kmalloc-16: Restoring 0xffff810101b45310-0xffff810101b45311=0x5a
next prev parent reply other threads:[~2007-09-20 7:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 12:39 2.6.23-rc6-mm1: BUG kmalloc-16: Object padding overwritten (sysfs?) 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 [this message]
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=20070920075353.GA6781@localhost.sw.ru \
--to=adobriyan@sw.ru \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.