From: Christoph Lameter <clameter@sgi.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: 2.6.25-rc8-mm2: FIX kmalloc-2048 (was Re: 2.6.25-rc8-mm2: IP: [<ffffffff802868f9>] __kmalloc+0x69/0x110)
Date: Mon, 14 Apr 2008 13:05:09 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0804141301580.7803@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20080414195613.GA4772@martell.zuzino.mipt.ru>
On Mon, 14 Apr 2008, Alexey Dobriyan wrote:
> I can reproduce semi-reliably (by kernel standards) corruption in
> kmalloc-2048. No idea if this can explain all "struct file" related
> oopses I saw, or SLUB free pointer corruption Pekka and Christoph are
> looking into.
The slub free pointer corruption is usually a result of the overwrites.
> Bytes b4 0xffff81017ff9d2c0: 62 ea ff ff 00 00 00 00 5a 5a 5a 5a 5a 5a 5a 5a
> Object 0xffff81017ff9d2d0: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
> Object 0xffff81017ff9d2e0: 6b 6b 00 18 f3 a2 9f 90 00 1b 38 af 22 49 08 00
> Object 0xffff81017ff9d2f0: 45 10 00 4c ff 59 40 00 40 11 86 ac c0 a8 00 2a
> Object 0xffff81017ff9d300: 50 fa a2 be 91 43 00 7b 00 38 54 d4 23 00 00 00
> Object 0xffff81017ff9d310: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> Object 0xffff81017ff9d320: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> Object 0xffff81017ff9d330: 00 00 00 00 4c ff 10 44 74 7f 6f 9d e4 c8 a2 4f
> Object 0xffff81017ff9d340: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> Redzone 0xffff81017ff9dad0: bb bb bb bb bb bb bb bb
> Padding 0xffff81017ff9db10: 5a 5a 5a 5a 5a 5a 5a 5a
>
> FIX kmalloc-2048: Restoring 0xffff81017ff9d2e2-0xffff81017ff9d8d9=0x6b
Looks like skb corruption. Would be helpful to have the complete output
though. Does the data in the restored range trigger any memories?
next prev parent reply other threads:[~2008-04-14 20:05 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-11 3:33 2.6.25-rc8-mm2 Andrew Morton
2008-04-11 6:28 ` 2.6.25-rc8-mm2: boot hang after "ACPI: using IOAPIC for interrupt routing" Alexey Dobriyan
2008-04-11 6:29 ` Alexey Dobriyan
2008-04-11 6:43 ` Pekka Enberg
2008-04-11 10:35 ` Pekka Enberg
2008-04-11 21:07 ` Alexey Dobriyan
2008-04-11 21:25 ` Pekka J Enberg
2008-04-11 23:09 ` Alexey Dobriyan
2008-04-11 9:57 ` 2.6.25-rc8-mm2 KAMEZAWA Hiroyuki
2008-04-11 10:23 ` 2.6.25-rc8-mm2 KAMEZAWA Hiroyuki
2008-04-11 10:34 ` 2.6.25-rc8-mm2 Pekka Enberg
2008-04-11 10:57 ` 2.6.25-rc8-mm2 KAMEZAWA Hiroyuki
2008-04-11 11:17 ` 2.6.25-rc8-mm2 KAMEZAWA Hiroyuki
2008-04-11 13:17 ` 2.6.25-rc8-mm2 KAMEZAWA Hiroyuki
2008-04-11 14:24 ` 2.6.25-rc8-mm2 Pekka Enberg
2008-04-14 3:13 ` 2.6.25-rc8-mm2 KAMEZAWA Hiroyuki
2008-04-11 13:40 ` 2.6.25-rc8-mm2 Adrian Bunk
2008-04-12 4:22 ` 2.6.25-rc8-mm2 Andrew Morton
2008-04-12 18:43 ` 2.6.25-rc8-mm2 Aneesh Kumar K.V
2008-04-13 7:45 ` 2.6.25-rc8-mm2 Michael Schmitz
2008-04-13 8:11 ` 2.6.25-rc8-mm2 Geert Uytterhoeven
2008-04-11 23:43 ` 2.6.25-rc8-mm2: panic involving mount_block_root and down the road Alexey Dobriyan
2008-04-12 0:59 ` 2.6.25-rc8-mm2: CONFIG_ATA_SFF: " Alexey Dobriyan
2008-04-12 6:52 ` Adrian Bunk
2008-04-12 10:02 ` Jeff Garzik
2008-04-13 0:45 ` Tejun Heo
2008-04-13 0:51 ` [mm patch] select ATA_SFF Adrian Bunk
2008-04-12 5:53 ` 2.6.25-rc8-mm2 Valdis.Kletnieks
2008-04-12 6:07 ` 2.6.25-rc8-mm2 Andrew Morton
2008-04-12 8:52 ` 2.6.25-rc8-mm2 - CONFIG_PROFILE_LIKELY broke again Valdis.Kletnieks
2008-04-12 9:41 ` 2.6.25-rc8-mm2 Valdis.Kletnieks
2008-04-12 10:47 ` 2.6.25-rc8-mm2 - ftraced chews 100% of a CPU Valdis.Kletnieks
2008-04-13 20:44 ` 2.6.25-rc8-mm2: IP: [<ffffffff802868f9>] __kmalloc+0x69/0x110 Alexey Dobriyan
2008-04-13 20:53 ` Andrew Morton
2008-04-14 16:18 ` Pekka Enberg
2008-04-14 18:00 ` Christoph Lameter
2008-04-14 9:51 ` Pekka J Enberg
2008-04-14 16:01 ` Pekka Enberg
2008-04-14 17:53 ` Christoph Lameter
2008-04-14 17:57 ` Christoph Lameter
2008-04-14 18:32 ` Alexey Dobriyan
2008-04-14 19:56 ` 2.6.25-rc8-mm2: FIX kmalloc-2048 (was Re: 2.6.25-rc8-mm2: IP: [<ffffffff802868f9>] __kmalloc+0x69/0x110) Alexey Dobriyan
2008-04-14 20:05 ` Christoph Lameter [this message]
2008-04-19 11:17 ` Alexey Dobriyan
2008-04-19 14:45 ` atl1 64-bit => 32-bit DMA borkage (reproducible, bisected) Alexey Dobriyan
2008-04-20 2:54 ` Jay Cliburn
2008-04-20 11:14 ` Alexey Dobriyan
2008-04-20 11:06 ` Jay Cliburn
2008-04-20 12:26 ` Alexey Dobriyan
2008-04-20 18:37 ` Jay Cliburn
2008-04-20 20:55 ` Alexey Dobriyan
2008-04-21 18:42 ` Chris Snook
2008-04-21 19:56 ` Alexey Dobriyan
2008-04-22 2:08 ` Jay Cliburn
2008-04-22 19:02 ` Alexey Dobriyan
2008-04-26 0:57 ` Jay Cliburn
2008-04-28 6:42 ` Alexey Dobriyan
2008-05-04 21:15 ` Alexey Dobriyan
2008-05-05 0:31 ` Jay Cliburn
2008-05-05 0:34 ` Jay Cliburn
2008-05-06 16:02 ` Jay Cliburn
2008-05-09 19:51 ` Alexey Dobriyan
2008-05-09 18:56 ` Chris Snook
2008-05-09 20:07 ` Alexey Dobriyan
2008-05-09 19:38 ` Jay Cliburn
2008-05-10 19:31 ` [PATCH] " Alexey Dobriyan
2008-05-11 1:58 ` Jay Cliburn
2008-04-14 8:07 ` BUG at __dentry_open [Was: 2.6.25-rc8-mm2] Jiri Slaby
2008-04-15 17:00 ` 2.6.25-rc8-mm2: Observed problems: Not a detailed bug report Zan Lynx
2008-04-15 18:42 ` Andrew Morton
2008-04-15 20:12 ` Rafael J. Wysocki
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.0804141301580.7803@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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
all inboxes | Powered by JetHome®