All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] IMQ - bug when doing ingress and egress shaping on the
Date: Mon, 31 Mar 2003 12:45:15 +0000	[thread overview]
Message-ID: <marc-lartc-104911486427244@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104909248609737@msgid-missing>

Kjell Chris Flor wrote:

>http://www.mail-archive.com/lartc@mailman.ds9a.nl/msg03827.html
>
>you can't add ingress and egress packets into 
>the same IMQ device from the same physical device.
>
>iptables -t mangle -A POSTROUTING -o eth0 -j IMQ
>iptables -t mangle -A PRETROUTING -i eth0 -j IMQ
>
>Is this problem solved?
>
>
>****************************************************
>
>Is it?
>
>
>Kjell
>  
>

i'm sorry to disapoint you, it is not solved and might possibly never be.
I'm thinking about dropping imq maintenance, i don't need it myself
anymore and due to lack of time i cannot provide even the most-requested
features. i think the imq users would be better of with a maintainer who
actually uses imq himself.

Volunteers are welcome!

If anyone wants to "fix" the issue described in this mail, it's 
basically a fact
of dropping dev->xmit_lock before reinjecting the packet in imq_xmit and
grabbing it back afterwards. look in net/sched/sch_generic.c::sch_restart()
in order to understand what to do exactly with the locks. make sure to
catch too deep recursion, one or two levels should be enough.


Bye,
Patrick

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      reply	other threads:[~2003-03-31 12:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-31  6:33 [LARTC] IMQ - bug when doing ingress and egress shaping on the same interface Kjell Chris Flor
2003-03-31 12:45 ` Patrick McHardy [this message]

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=marc-lartc-104911486427244@msgid-missing \
    --to=kaber@trash.net \
    --cc=lartc@vger.kernel.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.