From: Richard Fuchs <richard.fuchs@inode.info>
To: Scott Feldman <sfeldma@pobox.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: slab corruption in skb allocs
Date: Sun, 06 Mar 2005 19:40:23 +0100 [thread overview]
Message-ID: <422B4E97.4090303@inode.info> (raw)
In-Reply-To: <0a8f9833de8ba3f767f3b3211bbb693a@pobox.com>
Scott Feldman wrote:
> On Mar 5, 2005, at 11:10 AM, Richard Fuchs wrote:
>> looks like you are right, enabling NAPI in 2.6.7 does trigger this.
>>
>> what exactly is this?
> A bug in the driver. I have a hunch: please try this patch with 2.6.9
> or higher:
>
> http://marc.theaimsgroup.com/?l=linux-netdev&m=110726809431611&w=2
bingo, that fixes it. too bad neither this patch nor the removal of the
NAPI config option made it into 2.6.11...
>> also, does this affect the e1000 driver in any way?
> No. e1000 is a totally different driver/device with very similar name.
too bad, i was hoping for an explanation for some unexplainable crashes
i've been experiencing... ;)
cheers
richard
next prev parent reply other threads:[~2005-03-06 18:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 9:55 slab corruption in skb allocs Richard Fuchs
2005-03-04 11:53 ` Andrew Morton
2005-03-04 12:23 ` Richard Fuchs
2005-03-04 20:11 ` Matt Mackall
2005-03-04 21:19 ` Richard Fuchs
2005-03-04 21:27 ` Matt Mackall
2005-03-04 21:52 ` Richard Fuchs
2005-03-04 22:05 ` Matt Mackall
2005-03-04 22:51 ` Richard Fuchs
2005-03-05 18:25 ` Scott Feldman
2005-03-05 19:10 ` Richard Fuchs
2005-03-06 17:44 ` Scott Feldman
2005-03-06 18:40 ` Richard Fuchs [this message]
2005-03-07 5:07 ` Scott Feldman
2005-03-07 8:30 ` Richard Fuchs
2005-03-04 18:10 ` Dave Jones
2005-03-04 18:32 ` Richard Fuchs
2005-03-04 19:29 ` Richard Fuchs
2005-03-21 22:36 ` Andrew Morton
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=422B4E97.4090303@inode.info \
--to=richard.fuchs@inode.info \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfeldma@pobox.com \
/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