Messages in this thread | | | Date | Tue, 24 Feb 2004 23:03:18 -0800 | From | "David S. Miller" <> | Subject | Re: [BUG] 2.6.3 Slab corruption: errors are triggered when memory exceeds 2.5GB (correction) |
| |
On Wed, 25 Feb 2004 07:21:56 +0100 Manfred Spraul <manfred@colorfullife.com> wrote:
> 0x620 (1568) is behind the end of the actual eth frame. Who could modify > that?
At the end of the SKB data area is where we keep struct skb_shared_info, something is messing with the SKB state after a free it appears.
And since it's turning the debugging value 0x6b to 0x6a it must be the "atomic_t dataref;" that is being mucked with. - 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/
| |