From: Manfred Spraul <manfred@colorfullife.com>
To: Andrew Morton <akpm@osdl.org>
Cc: dsw@gelato.unsw.edu.au, linux-kernel@vger.kernel.org
Subject: Re: [BUG] 2.6.3 Slab corruption: errors are triggered when memory exceeds 2.5GB (correction)
Date: Tue, 24 Feb 2004 18:40:08 +0100 [thread overview]
Message-ID: <403B8C78.2020606@colorfullife.com> (raw)
In-Reply-To: <20040223225659.4c58c880.akpm@osdl.org>
Andrew Morton wrote:
>Actually, it's often caused by someone doing atomic_dec_and_test() against
>something which was already freed.
>
The previous user is always kfree_skbmem - I would be surprised if there
are atomic operations against the skb data area.
Darren, could you try the latest bk snapshot? Linus yesterday merged a
patch that hexdumps the affected bytes. We must try to find a pattern -
always same offset into a page, always same physical address, always
same offset into the object, etc.
--
Manfred
next prev parent reply other threads:[~2004-02-24 17:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 6:38 [BUG] 2.6.3 Slab corruption: errors are triggered when memory exceeds 2.5GB (correction) Manfred Spraul
2004-02-24 6:56 ` Andrew Morton
2004-02-24 8:45 ` Darren Williams
2004-02-24 17:40 ` Manfred Spraul [this message]
2004-02-25 0:58 ` Darren Williams
2004-02-25 1:05 ` Anton Blanchard
2004-02-25 6:21 ` Manfred Spraul
2004-02-25 7:03 ` David S. Miller
2004-02-25 7:22 ` Andrew Morton
2004-02-25 8:24 ` Darren Williams
2004-02-25 17:18 ` Manfred Spraul
2004-02-26 0:30 ` Darren Williams
2004-02-25 8:55 ` Darren Williams
2004-02-25 10:18 ` Peter Chubb
2004-02-25 6:17 ` Darren Williams
-- strict thread matches above, loose matches on Subject: below --
2004-02-24 0:22 [BUG] 2.6.3 Slab corruption: errors are triggered when memory exceeds 2GB Darren Williams
2004-02-24 1:14 ` [BUG] 2.6.3 Slab corruption: errors are triggered when memory exceeds 2.5GB (correction) Darren Williams
2004-02-24 1:14 ` Darren Williams
2004-02-26 1:09 ` Darren Williams
2004-02-24 21:44 ` Darren Williams
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=403B8C78.2020606@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=akpm@osdl.org \
--cc=dsw@gelato.unsw.edu.au \
--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.