All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: James Bourne <jbourne@hardrock.org>,
	linux-kernel@vger.kernel.org, coreteam@netfilter.org
Subject: Re: [netfilter-core] 2.4.23/others and ip_conntrack causing hangs
Date: Tue, 02 Dec 2003 01:20:15 +0100	[thread overview]
Message-ID: <3FCBDABF.6080804@trash.net> (raw)
In-Reply-To: <20031201015604.816D52C06F@lists.samba.org>

Rusty Russell wrote:

>Unfortunately, some packets are still referencing connections, so the
>module *cannot* go away.  Figuring out exactly where the packets are
>referenced from is the fun part.  We explicitly drop the reference in
>ip_local_deliver_finish() for exactly this reason.  Perhaps there is
>somewhere else we should be doing the same thing.
>  
>
Perhaps in dev_queue_xmit ? Otherwise packets stuck in queues hold
references to conntracks. Loopback traffic might cause some trouble
because the "previously seen?" expection in ip_conntrack_core wouldn't
work anymore.

Best regards,
Patrick

>Hope that clarifies,
>Rusty.
>--
>  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
>-
>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/
>  
>



  reply	other threads:[~2003-12-02  0:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-30 19:21 2.4.23/others and ip_conntrack causing hangs James Bourne
2003-12-01  0:22 ` [netfilter-core] " Rusty Russell
2003-12-02  0:20   ` Patrick McHardy [this message]
2003-12-02  6:33     ` Rusty Russell
2003-12-02 23:18       ` 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=3FCBDABF.6080804@trash.net \
    --to=kaber@trash.net \
    --cc=coreteam@netfilter.org \
    --cc=jbourne@hardrock.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /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.