Re: Kernel Oops when using the Netfilter QUEUE target

From: Rusty Russell (rusty@rustcorp.com.au)
Date: Fri Apr 27 2001 - 08:42:15 EST

Next message: Mike Galbraith: "Re: #define HZ 1024 -- negative effects?"
Previous message: Lawrence Gold: "Oopses under 2.4.4pre8 with Tbird 1.2GHz/Epox 8kta3"
In reply to: Martin Clausen: "Re: Kernel Oops when using the Netfilter QUEUE target"
Next in thread: Keith Owens: "Re: Kernel Oops when using the Netfilter QUEUE target"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

In message <20010427004801.A3464@ostenfeld.dk> you write:
> On Wed, Apr 25, 2001 at 04:24:46PM +1000, James Morris wrote:
> > Please try the patch below.
>
> So i did and it seems to work just fine (= no more oops') under 2.4.3/2.4.2-a

James, I only glanced at the patch, but IIRC it just did
route_me_harder() on everything. This is, unfortunately, no longer
"Best Practice": the prevailing trend is to reroute only when
something has actually been changed, to avoid overriding the socket
binding, etc.

See mangle for an example (store old values, see if they changed). I
think this would be more complex, but still possible in your case, no?

Thanks,
Rusty.

--
Premature optmztion is rt of all evl. --DK
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Next message: Mike Galbraith: "Re: #define HZ 1024 -- negative effects?"
Previous message: Lawrence Gold: "Oopses under 2.4.4pre8 with Tbird 1.2GHz/Epox 8kta3"
In reply to: Martin Clausen: "Re: Kernel Oops when using the Netfilter QUEUE target"
Next in thread: Keith Owens: "Re: Kernel Oops when using the Netfilter QUEUE target"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Mon Apr 30 2001 - 21:00:19 EST