All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Oester <kernel@linuxace.com>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: Deadlocks
Date: Mon, 21 Jun 2004 21:31:29 -0700	[thread overview]
Message-ID: <20040622043129.GA15906@linuxace.com> (raw)
In-Reply-To: <40D62FDB.8090904@trash.net>

On Mon, Jun 21, 2004 at 02:46:19AM +0200, Patrick McHardy wrote:
> Not sure either, but it's a start. Have you tried running the box with
> netfilter debugging enabled ? Please also apply the ip_nf_assert fix
> from pom-ng, otherwise CONFIG_NETFILTER_DEBUG won't help much.
> BTW: Is the box a router or is conntrack running on the FTP server
> itself ?

The box is a router -- the ftp server is a separate box.

Thanks for the tip on the ip_nf_assert patch - I'd been running with debugging
enabled but wondered why I never saw anything...

Now that I enabled debugging (for real), I hit this one a few hundred times
per minute:

NF_IP_ASSERT: net/ipv4/netfilter/ip_conntrack_core.c:717(init_conntrack)

which is in this chunk of code:

        if (expected) {
                DEBUGP("conntrack: expectation arrives ct=%p exp=%p\n",
                        conntrack, expected);
                /* Welcome, Mr. Bond.  We've been expecting you... */
                IP_NF_ASSERT(master_ct(conntrack));
                __set_bit(IPS_EXPECTED_BIT, &conntrack->status);
                conntrack->master = expected;
                expected->sibling = conntrack;
                LIST_DELETE(&ip_conntrack_expect_list, expected);
                expected->expectant->expecting--;
                nf_conntrack_get(&master_ct(conntrack)->infos[0]);
        }


Other than being mildly annoying, this doesn't explain the deadlocks,
so I'll let it run for a few more days...

Phil

  reply	other threads:[~2004-06-22  4:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-09 18:09 Deadlocks Phil Oester
2004-06-10  8:07 ` Deadlocks Jozsef Kadlecsik
2004-06-10 15:02   ` Deadlocks Phil Oester
2004-06-13 19:58 ` Deadlocks Patrick McHardy
2004-06-15  4:47   ` Deadlocks Phil Oester
2004-06-15  6:23     ` Deadlocks Patrick McHardy
2004-06-17 15:59       ` Deadlocks Phil Oester
2004-06-17 16:20         ` Deadlocks Patrick McHardy
2004-06-18 17:12           ` Deadlocks Phil Oester
2004-06-21  0:46             ` Deadlocks Patrick McHardy
2004-06-22  4:31               ` Phil Oester [this message]
2004-06-22  9:52                 ` Deadlocks Patrick McHardy
2004-06-29 17:54               ` Deadlocks Phil Oester
2004-06-29 18:00                 ` Deadlocks Patrick McHardy
2004-06-29 20:09                   ` Deadlocks Phil Oester
2004-06-30  9:50                     ` Deadlocks Patrick McHardy
2004-07-01 16:12                       ` Deadlocks 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=20040622043129.GA15906@linuxace.com \
    --to=kernel@linuxace.com \
    --cc=kaber@trash.net \
    --cc=netfilter-devel@lists.netfilter.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.