From: Daniel Drake <dsd@gentoo.org>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: netdev@vger.kernel.org, mcclung@nebrwesleyan.edu
Subject: Re: [RFT] sky2 vs iptables
Date: Sat, 16 Sep 2006 23:01:46 -0400 [thread overview]
Message-ID: <450CBA9A.4040705@gentoo.org> (raw)
In-Reply-To: <20060906141651.116aa758@localhost.localdomain>
Stephen Hemminger wrote:
> On Tue, 05 Sep 2006 21:36:24 -0400
> Daniel Drake <dsd@gentoo.org> wrote:
>> There's a strange sky2 bug on the Gentoo bugzilla:
>> http://bugs.gentoo.org/show_bug.cgi?id=136508
>>
>> sky2 seems to work OK, but breaks as soon as the iptables ruleset is
>> loaded. Nothing can be pinged, etc.
>>
>> Can someone try and reproduce this? The iptables rule script has been
>> uploaded here:
>> http://bugs.gentoo.org/attachment.cgi?id=95694&action=view
>>
>> The very last command in that file is the one which produces an error
>> and stops everything working:
>>
>> iptables: Unknown error 18446744073709551615
>>
>> Apparently a sky2 null deref has also been seen at this point, although
>> I don't have further details on that.
>
> It might be an artifact of the way sky2 was allocating receive buffers.
> Bridge-netfilter was assuming header space in the buffer, and would corrupt
> other memory, maybe iptables is assuming as well. This makes sky2
> use dev_alloc_skb that reserves space.
> -----------------------
> Subject: sky2: use dev_alloc_skb for receive buffers
Unfortunately the problem still exists with this patch. Any other ideas?
Daniel
next prev parent reply other threads:[~2006-09-17 3:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-06 1:36 [RFT] sky2 vs iptables Daniel Drake
2006-09-06 21:16 ` Stephen Hemminger
2006-09-17 3:01 ` Daniel Drake [this message]
2006-09-21 23:37 ` Stephen Hemminger
2006-10-04 14:11 ` Daniel Drake
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=450CBA9A.4040705@gentoo.org \
--to=dsd@gentoo.org \
--cc=mcclung@nebrwesleyan.edu \
--cc=netdev@vger.kernel.org \
--cc=shemminger@osdl.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.