From: Andrew Morton <akpm@digeo.com>
To: "David S. Miller" <davem@redhat.com>
Cc: tomlins@cam.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, rusty@rustcorp.com.au,
laforge@netfilter.org
Subject: Re: Slab corruption mm3 + davem fixes
Date: Sun, 11 May 2003 15:15:06 -0700 [thread overview]
Message-ID: <20030511151506.172eee58.akpm@digeo.com> (raw)
In-Reply-To: <1052690490.4471.2.camel@rth.ninka.net>
"David S. Miller" <davem@redhat.com> wrote:
>
> On Sun, 2003-05-11 at 09:21, Ed Tomlinson wrote:
> > I am also seeing this on 69-bk (as of Sunday morning)
> ...
> > On May 10, 2003 11:19 pm, Ed Tomlinson wrote:
> > > I looked at my logs and found the following error in it. My kernel is
> > > 69-mm3 with two davem fixes on it.
> ...
> > > May 10 22:41:06 oscar kernel: Call Trace:
> > > May 10 22:41:06 oscar kernel: [__slab_error+30/32] __slab_error+0x1e/0x20
> > > May 10 22:41:06 oscar kernel: [check_poison_obj+376/384]
> > > check_poison_obj+0x178/0x180 May 10 22:41:06 oscar kernel:
> > > [kmalloc+221/392] kmalloc+0xdd/0x188 May 10 22:41:06 oscar kernel:
> > > [alloc_skb+64/240] alloc_skb+0x40/0xf0 May 10 22:41:06 oscar kernel:
>
> Yeah, more bugs in the NAT netfilter changes. Debugging this one
> patch is becomming a full time job :-(
>
> This should fix it. Rusty, you're computing checksums and mangling
> src/dst using header pointers potentially pointing to free'd skbs.
>
Did you mean to send a one megabyte diff?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-05-11 22:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-11 3:19 Ed Tomlinson
2003-05-11 16:21 ` Ed Tomlinson
2003-05-11 22:01 ` David S. Miller
2003-05-11 22:15 ` Andrew Morton [this message]
2003-05-11 21:24 ` David S. Miller
2003-05-11 22:34 ` David S. Miller
2003-05-12 7:44 ` Ed Tomlinson
2003-05-12 6:42 ` David S. Miller
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=20030511151506.172eee58.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=davem@redhat.com \
--cc=laforge@netfilter.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rusty@rustcorp.com.au \
--cc=tomlins@cam.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox