All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Phil Oester <kernel@linuxace.com>
Cc: netfilter-devel@lists.netfilter.org, pablo@eurodev.net
Subject: Re: [PATCH] Fix hang on netfilter module unload
Date: Tue, 15 Mar 2005 20:25:17 +0100	[thread overview]
Message-ID: <4237369D.8080408@trash.net> (raw)
In-Reply-To: <20050315172330.GA3130@linuxace.com>

Phil Oester wrote:
>>So we are leaking conntracks for some reason that we must diagnose.
> 
> 
> No...the app is leaking skbs.  Since the skb never goes away (at least
> until closing the app), the conntrack can thus not go away.  Isn't
> it better for us to work around stupid apps like this?  Seems preferable
> to not hang the box on iptables restart/unload, eh?

I guess by leaking you mean doesn't pull them of the receive queue.
Anyhow, the reference to the conntrack is dropped before packets
are delivered to the protocols, so this can't be the reason. Do
you have a reproducable test-case ?

>>But this is cheating, of course that the module will unload if we set 
>>all refcounts to 1 we won't spin forever in the i_see_dead_people loop 
>>but we are leaking somewhere anyway.
> 
> 
> Well, again, the admin has asked to unload iptables -- should we unload,
> or lockup the box?

Unload - after fixing the leaks :) If we cover it up this way it will
never get fixed properly.

Regards
Patrick

  reply	other threads:[~2005-03-15 19:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-15  5:06 [PATCH] Fix hang on netfilter module unload Phil Oester
2005-03-15 12:57 ` Pablo Neira
2005-03-15 17:23 ` Phil Oester
2005-03-15 19:25   ` Patrick McHardy [this message]
2005-03-15 19:46     ` Phil Oester
2005-03-15 19:53       ` Patrick McHardy
2005-03-15 20:09         ` Patrick McHardy
2005-03-15 21:48           ` Patrick McHardy
2005-03-15 20:25         ` Phil Oester

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=4237369D.8080408@trash.net \
    --to=kaber@trash.net \
    --cc=kernel@linuxace.com \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=pablo@eurodev.net \
    /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.