All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andrew Hall" <temp02@bluereef.com.au>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: IMQ device problems with iptables: dead looping?
Date: Wed, 09 Apr 2003 00:15:40 +0000	[thread overview]
Message-ID: <marc-lartc-104984751920668@msgid-missing> (raw)

Hi Patrick,

Just wondering if you've had a chance to get your new version of the IMQ
device completed as yet to fix this deadlooping problem?

thanks and regards,

Andrew.
----- Original Message -----
From: "Patrick McHardy" <kaber@trash.net>
To: "Andrew Hall" <temp02@bluereef.com.au>
Cc: <lartc@mailman.ds9a.nl>
Sent: Wednesday, February 19, 2003 9:43 PM
Subject: Re: IMQ device problems with iptables: dead looping?


> Andrew Hall wrote:
>
> >Hello,
> >
> >I am using the IMQ with iptables (latest versions) and asking all packets
to
> >be enqueued to IMQ0 from both prerouting and postrouting (using different
> >iptables rules to mark different streams). When I do this I get the
kernel
> >saying:
> >
> >"Dead loop on netdevice imq0, fix it urgently!" and communications stop
> >intermittently. If I remove the jump from either preroute or postroute it
> >works fine but won't work together.
> >
> >Is this what is mean't to happen, because as far as I can see there is no
> >loop happening here?
> >
>
> You probably forward packets. The loop happening ist
> input-device -> prerouting -> imq (xmit_lock locked) -> reinject -> ...
> -> postrouting -> imq (LOCKED!!)
>
> To avoid this one has to drop xmit_lock in imq_xmit function before
> reinjecteing and grab it back afterwards.
> unfortunately this allows for endless recursion which is not possible in
> the kernel due to limited stack space.
> I've completed a version which should hopefully fix this as many people
> requested such a feature.
> I haven't released it yet because i have to do alot for my university
> atm and haven't got the time for testing
> although i promised the new version to some people for january ;(
> In about two weeks my semester-vacation start, i hope to release the new
> version very quickly afterwards.
>
> Thanks for your patience,
> Patrick
>
>

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

             reply	other threads:[~2003-04-09  0:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-09  0:15 Andrew Hall [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-19 11:43 [LARTC] Re: IMQ device problems with iptables: dead looping? Patrick McHardy

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-104984751920668@msgid-missing \
    --to=temp02@bluereef.com.au \
    --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.