From: Rusty Russell <rusty@rustcorp.com.au>
To: James Bourne <jbourne@hardrock.org>
Cc: linux-kernel@vger.kernel.org, coreteam@netfilter.org
Subject: Re: [netfilter-core] 2.4.23/others and ip_conntrack causing hangs 
In-reply-to: Your message of "Sun, 30 Nov 2003 12:21:33 PDT."
             <Pine.LNX.4.44.0311301204520.2148-100000@cafe.hardrock.org> 
Date: Mon, 01 Dec 2003 11:22:59 +1100
Message-Id: <20031201015604.816D52C06F@lists.samba.org>
Sender: linux-kernel-owner@vger.kernel.org

In message <Pine.LNX.4.44.0311301204520.2148-100000@cafe.hardrock.org> you writ
e:
> Hi all,
> I wanted to bring up an issue with ip_conntrack in 2.4.23, 2.4.22, and at
> least 2.4.21 (sorry, didn't try 2.4.20).
> 
> The issue is that as long as there are connections being tracked, the
> ip_conntrack module will not unload.  I can understand why this might be,
> but the problem is that ip_conntrack will hang rmmod and modprobe -r until
> such time as all the connections have been closed.
> 
> I think we need something like an ip_conntrack_flush or else completely drop
> the connections when the module is unloaded (as previously done) as this
> becomes an issue for people who need to drop their ip_tables and reload the
> modules (perhaps to correct other issues) especially ip_conntrack...  

Um, this is exactly what the code does on unload: an explicit flush.

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.

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/