Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933251AbYGQXQL (ORCPT ); Thu, 17 Jul 2008 19:16:11 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1759363AbYGQXPv (ORCPT ); Thu, 17 Jul 2008 19:15:51 -0400 Received: from yw-out-2324.google.com ([74.125.46.31]:51050 "EHLO yw-out-2324.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933271AbYGQXPu (ORCPT ); Thu, 17 Jul 2008 19:15:50 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=AX70ErqtF2y7lkEmo1OoICFKpJpT2ODGy03SPnlls04DlvjSxkdL6UBpeOlPmqiFuJ nzzGlVMt+keY6P8U1NrLsxPErbwCgz1n+6+xJb4Q+VPWUNj5995OznM70ohiPvhciFb3 VQ7So5mPbVzWxXwnPcw3WCs+dlCZ01zzZT82I= Message-ID: <19f34abd0807171615s5b477d4cr22d3e9444bcf65df@mail.gmail.com> Date: Fri, 18 Jul 2008 01:15:47 +0200 From: "Vegard Nossum" To: "Ingo Molnar" Subject: Re: [bug, netconsole, SLUB] BUG skbuff_head_cache: Poison overwritten Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org, "Pekka Enberg" , "Rafael J. Wysocki" In-Reply-To: <20080717214222.GA29449@elte.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080717214222.GA29449@elte.hu> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1459 Lines: 39 On Thu, Jul 17, 2008 at 11:42 PM, Ingo Molnar wrote: > > A regression to v2.6.26: > > I started getting this skb-head corruption message today, on a T60 > laptop with e1000: > > PM: Removing info for No Bus:vcs11 > device: 'vcs11': device_create_release > ============================================================================= > BUG skbuff_head_cache: Poison overwritten > ----------------------------------------------------------------------------- > > INFO: 0xf658ae9c-0xf658ae9c. First byte 0x6a instead of 0x6b 1. Notice the range. It's just a single byte. 2. Notice the value. It's just a ++. Probably a stray increment of a uint8_t somewhere on a freed object? The offset from the beginning of the object is 0xf658ae9c - 0xf658ae00 = 0x9c. How big is a struct sk_buff? Hm.. it is in fact quite big. Now what member has offset 0x9c? Seems to depend on your config. Is there any way you can figure it out, Ingo? I'll try it with your config too. Vegard -- "The animistic metaphor of the bug that maliciously sneaked in while the programmer was not looking is intellectually dishonest as it disguises that the error is the programmer's own creation." -- E. W. Dijkstra, EWD1036 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/