* Deadlock in netfilter code (ftp-conntrack)
@ 2004-08-11 13:28 Max Kellermann
2004-08-11 13:51 ` Patrick McHardy
0 siblings, 1 reply; 2+ messages in thread
From: Max Kellermann @ 2004-08-11 13:28 UTC (permalink / raw)
To: netfilter-devel
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?
I hope KDB will stay up a bit longer on the next crash, so I can
locate the bug. You will hear from me again, hopefully with a patch
file attached..
Max
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Deadlock in netfilter code (ftp-conntrack)
2004-08-11 13:28 Deadlock in netfilter code (ftp-conntrack) Max Kellermann
@ 2004-08-11 13:51 ` Patrick McHardy
0 siblings, 0 replies; 2+ messages in thread
From: Patrick McHardy @ 2004-08-11 13:51 UTC (permalink / raw)
To: Max Kellermann; +Cc: netfilter-devel
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2004-08-11 13:51 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-08-11 13:28 Deadlock in netfilter code (ftp-conntrack) Max Kellermann
2004-08-11 13:51 ` Patrick McHardy
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.