All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Max Kellermann <max@duempel.org>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: Deadlock in netfilter code (ftp-conntrack)
Date: Wed, 11 Aug 2004 15:51:58 +0200	[thread overview]
Message-ID: <411A247E.3020305@trash.net> (raw)
In-Reply-To: <20040811132802.GA20963@swift.xantronnet.de>

Max Kellermann wrote:

>Hi,
>
>I am currently hunting a deadlock bug in the netfilter code on severel
>of our servers. I will provide more information when I can analyze the
>next crash.
>
>Two servers are crashing once a week since we upgraded to 2.6.7
>(2.4.22 before; 2.4.23+ seemed to have a similar problem, though I
>never debugged them). All servers are dual Xeon 2.6 GHz with 2 GB
>memory, CCISS controller. Hyperthreading is enabled, making 4 virtual
>CPUs. I used KDB remotely to debug (the Compaq boxes have a web
>interface with a really ugly applet for remote console access - I have
>no physical access to the servers).
>
>Today, all CPUs except one hung in ip_ct_refresh(), trying to get a
>write lock. The last CPU waited for a spinlock in ip_nat_ftp.c,
>function help(). Unfortunately, KDB crashed before I could find out
>more. On the previous crash, I was able to manually revive the server
>by resetting the spinlock directly in kernel memory with KDB twice.
>
>Is this a known bug in netfilter?
>  
>
There is a known deadlock condition in the ftp/irc helper which
matches your description. Please try the helper-locking-fix from
patch-o-matic-ng and let us know if it helped.

Regards
Patrick

      reply	other threads:[~2004-08-11 13:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-11 13:28 Deadlock in netfilter code (ftp-conntrack) Max Kellermann
2004-08-11 13:51 ` Patrick McHardy [this message]

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=411A247E.3020305@trash.net \
    --to=kaber@trash.net \
    --cc=max@duempel.org \
    --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.