netdev
[Top] [All Lists]

Re: iptables breakage WAS(Re: dummy as IMQ replacement

To: Andy Furniss <andy.furniss@xxxxxxxxxxxxx>
Subject: Re: iptables breakage WAS(Re: dummy as IMQ replacement
From: jamal <hadi@xxxxxxxxxx>
Date: 25 Mar 2005 07:39:06 -0500
Cc: Harald Welte <laforge@xxxxxxxxxxxx>, Patrick McHardy <kaber@xxxxxxxxx>, Remus <rmocius@xxxxxxxxxxxxxx>, netdev@xxxxxxxxxxx, Nguyen Dinh Nam <nguyendinhnam@xxxxxxxxx>, Andre Tomt <andre@xxxxxxxx>, syrius.ml@xxxxxxxxxx, Damion de Soto <damion@xxxxxxxxxxxx>
In-reply-to: <1111749220.1092.457.camel@xxxxxxxxxxxxxxxx>
Organization: jamalopolous
References: <1107123123.8021.80.camel@xxxxxxxxxxxxxxxx> <00c301c524b4$938cd240$6e69690a@RIMAS> <1110379135.1091.143.camel@xxxxxxxxxxxxxxxx> <1110416767.1111.76.camel@xxxxxxxxxxxxxxxx> <025501c52552$2dbf87c0$6e69690a@RIMAS> <1110453757.1108.87.camel@xxxxxxxxxxxxxxxx> <423B7BCB.10400@xxxxxxxxxxxxx> <1111410890.1092.195.camel@xxxxxxxxxxxxxxxx> <423F41AD.3010902@xxxxxxxxxxxxx> <1111444869.1072.51.camel@xxxxxxxxxxxxxxxx> <423F71C2.8040802@xxxxxxxxxxxxx> <1111462263.1109.6.camel@xxxxxxxxxxxxxxxx> <42408998.5000202@xxxxxxxxxxxxx> <1111550254.1089.21.camel@xxxxxxxxxxxxxxxx> <4241C478.5030309@xxxxxxxxxxxxx> <1111607112.1072.48.camel@xxxxxxxxxxxxxxxx> <4241D764.2030306@xxxxxxxxxxxxx> <1111612042.1072.53.camel@xxxxxxxxxxxxxxxx> <4241F1D2.9050202@xxxxxxxxxxxxx> <4241F7F0.2010403@xxxxxxxxxxxxx> <1111625608.1037.16.camel@xxxxxxxxxxxxxxxx> <424212F7.10106@xxxxxxxxxxxxx> <1111663947.1037.24.camel@xxxxxxxxxxxxxxxx> <1111665450.1037.27.camel@xxxxxxxxxxxxxxxx> <4242DFB5.9040802@xxxxxxxxxxxxx> <1111749220.1092.457.camel@xxxxxxxxxxxxxxxx>
Reply-to: hadi@xxxxxxxxxx
Sender: netdev-bounce@xxxxxxxxxxx
On Fri, 2005-03-25 at 06:13, jamal wrote:

> I have reproduced this as well ;-> Reproduced typically means it will be
> fixed!
> I gotta give it to you - you have helped isolate more bugs in this one
> session than all others in the past summed up.
> 

Dang - this is a _serious_  kernel bug. I went back to some of the rcx
kernels pre-2611 and its there too.
Essentially what happens is once you enter netlink from user space
you cant go back in to query.

I am attaching a workaround patch for tc - Actually it is a solution -
but this means we have a kernel bug that needs investigation. In other
words we close that theres an issue for mirred.

cheers,
jamal

Attachment: p2_mirred
Description: Text document

<Prev in Thread] Current Thread [Next in Thread>